Hi all,
I have been looking at creating a library to simplify some of the DirectoryServices stuff but I am getting bogged down.
I just can't think of a good way to design a library like this that doesn't repeat a lot of stuff but make it easy for people to use. The library will be used in asp.net apps so it needs to support that.
At the moment i just have a bunch of disconnected static methods for doing things like adding a user, deleting a user, adding a group, getting group info, etc.
Thanks,
Jacob
-
Jachin
Complexity=Stupidity
-
blowdart
Peek-a-boo
Jachin wrote:Hi all,
I have been looking at creating a library to simplify some of the DirectoryServices stuff but I am getting bogged down.
I just can't think of a good way to design a library like this that doesn't repeat a lot of stuff but make it easy for people to use. The library will be used in asp.net apps so it needs to support that.
At the moment i just have a bunch of disconnected static methods for doing things like adding a user, deleting a user, adding a group, getting group info, etc.
Thanks,
Jacob
Lord knows it needs it, directory services is awful.
I'd look at abstracting the properties and values out of that nasty collection to some sort of dictionary object as well as adding properties for the most common properties, then abstract a user out; then a group. And in the group look at holding your user objects if necessary (although that's a lot of lookups)
Remember that group information for the current user is held the in principal object for that context.
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.