Making DirectoryServices Provider somewhat RFC 2253 compliant

Topics: Developer Forum
Sep 10, 2008 at 12:49 AM
After looking at LdapPath.Parse() and testing the provider against some of the Test OU with special names, I see that enhance needed to allow custom names.
For example, OU with these names all failed on set-location
"#hello", ",cn=","\#homeserverëort", "Nääs, Peter"
Is there plan to accommodate the special characters for 1.2 release?

Sep 24, 2008 at 10:23 PM
We don't have plans to address it at this time.  However if you are interested in tackling this problem we would love to have you contribute.  The person who originally added the AD provider isn't very active on the project at the moment so we could use some help.  :-)
Sep 24, 2008 at 11:45 PM
Sure, No problem.  Is there guidance on how to submit patches?
Oct 1, 2008 at 2:47 AM
Check out this link for details on how to submit a patch.