C# Tutorials and offshore development in India
    Tutorials   Resources   Forum   Communities   Interview   Jobs   Projects   Offshore Development    
Silverlight Tutorials | Mentor | Code Converter | Articles | Code Factory | Computer Jokes | Members | Peer Appraisal | IT Companies | Bookmarks | Revenue Sharing |


Prizes & Awards
My Profile



Active Members
TodayLast 7 Days more...

New Feature: Community Sites: Create your own .NET community website and start earning from Google AdSense ! It's Free !




Directory services programming in C# 2.0


Posted Date: 06 Aug 2007    Resource Type: Articles    Category: .NET Framework

Posted By: Vikram Singh Kshatriya       Member Level: Gold
Rating:     Points: 7



Introduction


Earlier to .NET framework 2.0 the System.Directory Services namespce was used to program for directory services .This namespace contains the classes that are created by keeping the MS Active directory in mind .By using these classes we can programmatically manage Active directory and other directory services as well .Now .NET framework 2.0 includes the new namespace that supports to all LDAP enabled Directory services.
The System.DirectoryServices.Protocols namespace provides the methods defined in the Lightweight Directory Access Protocol (LDAP) version 3 (V3) and Directory Services Markup Language (DSML) version 2.0 (V2) standards.
The System.DirectoryServices.Protocols namespace now includes proper LDAP classes suitable for use in the middle-tier which provide all the functionality present in WLDAP32.DLL. When it absolutely, postively has to be LDAP in the middle tier, this is a godsend for .NET developers. Because after all, in its essential form, LDAP really is pretty simple and lightweight. Directory objects have attributes, and attributes have values, and that sort of hierarchical relationship should be second nature in the era of XML.



System.DirectoryServices vs. System.DirectoryServices.Protocols



One of the issues with System.DirectoryServices is cleaning up all of the connections quick enough in a high load environment. As I began to understand the underlying characteristics of System.DirectoryServices – was if you need to control cleanup of connections use System.DirectoryServices.Protocols.

Fast Concurrent Bind isn’t really a bind


One of the things that S.DS.P supports is the idea of a Fast Concurrent Bind. Basically, check my credentials to make sure that they’re OK – and don’t do anything else. I tried using Fast Concurrent Bind (because it is the fastest way to validate a user) to bind to a connection and then do a search.


Summary



There are definitely the improvement to the earlier version of the directory services SDK.Some classes that are in this new namspaces are listed below :-

LdapConnection
DirectoryResponse
DirectoryRequest etc.




Responses


No responses found. Be the first to respond and make money from revenue sharing program.

Feedbacks      
Popular Tags   What are tags ?   Search Tags  
Programming in C# 2.0  .  Directory services  .  

Post Feedback


This is a strictly moderated forum. Only approved messages will appear in the site. Please use 'Spell Check' in Google toolbar before you submit.
You must Sign In to post a response.
Next Resource: Page Directives in ASP.NET 2.0
Previous Resource: Cross Page Posting In ASP.NET
Return to Discussion Resource Index
Post New Resource
Category: .NET Framework


Post resources and earn money!
 
Related Resources



dotNet Slackers   BizTalk Adaptors    Web Design

audio conferencing services

Contact Us    Privacy Policy    Terms Of Use