[RESOLVED] Looping Through the DirectoryEntry.Children Objects Doesn't Pull All Attribute Names

[weirddemon]

In my loop, I'm adding the property name and the value to a custom class.

foreach (PropertyValueCollection p in ChildObject.Properties)
                                {
                                    ActiveDirectoryAttributeList ADAList = new ActiveDirectoryAttributeList();
                                    ADAList.Attribute = p.PropertyName;
                                    ADAList.AttributeValue = p.Value.ToString();
                                    ChildNode.Attributes.Add(ADAList);
                                }

I'm able to pull some attributes, but not all of them. Below is an example of what my app pulls and what ADSI Edit pulls.

ADSI Edit:



My app:



Any ideas on why it's not pulling everything?

[techgnome]

It is... and it isn't... it's pulling the data that IS there... the attributes that ARE set... I'm thinking that ADSI Edit knows there are other possible attributes on the selected node... but they are not set.
It's like in XML, if you know the schema, you know what to expect... so you know what attributes/whatever are not set... even though the data itself may only have 3 of the 6 attributes set...

-tg

[kfcSmitty]

How are you doing your initial search? I've had several occasions where I've needed to explicitly specify a property I'm searching for when accessing our LDAP server.

When using a DirectorySearcher, you can do

DirectorySearcher search = new DirectorySearcher(<DirectoryEntry object>);
search.PropertiesToLoad.Add("keythatdoesntshowup");