Hi. Does anybody have a reasonable pros/cons list of whether to use activeds.tbl or the directoryservices namespace? I would appreciate not to use the activeds.tbl because of the interop (instructs), but someone told me that directoryservices does the same
thing? Anyone got an opinion. /Foged
DirectoryServices is basically one big managed wrapper around ADSI. There are some things that are more easily accomplished using the IADs interfaces (activeds.tbl), however the same is true about the DirectoryEntry and DirectorySearcher (searching comes to
mind quickly). Basically, I am not sure you are going to see a lot of difference performance-wise between using InterOp and calling ActiveDs or using DirectoryServices which uses InterOp anyway. I would suggest using DirectoryServices for new development when
possible, since that seems to be the programming model going forward and it is likely to remain that way if/when a purely managed version of ADSI/DirectoryServices is created.
Is there many other good example of using system.directoryservices other than http://msdn.microsoft.com/library/default.asp?url=/library/en-us/netdir/netds/adding_directory_objects.asp I can find heaps on using iads (there is a comprehensive one on adding a
user on msdn) but I can't find much on system.directoryservices. Particularly interested in the Add/Modify, I feel I have mastered the directorysearcher and enumerating groups/users and their details.
Foged
Member
370 Points
74 Posts
ActiveDs.tlb vs DirectoryServices
Oct 16, 2003 12:50 PM|LINK
dunnry
Star
9098 Points
1806 Posts
Re: ActiveDs.tlb vs DirectoryServices
Oct 16, 2003 09:26 PM|LINK
Weblog
The Book
LDAP Programming Help
Voldo
Member
145 Points
29 Posts
Re: ActiveDs.tlb vs DirectoryServices
Oct 22, 2003 01:14 AM|LINK