-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Provide System.DirectoryServices.Protocols package readme #93518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide System.DirectoryServices.Protocols package readme #93518
Conversation
|
Tagging subscribers to this area: @dotnet/area-system-directoryservices, @jay98014 Issue DetailsFill out details for the See #92228
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| It primarily utilizes the `LdapConnection` type for interacting with LDAP servers, utilizing system native libraries to establish TCP/IP or UDP LDAP connections. | |
| It primarily uses the `LdapConnection` type for interacting with LDAP servers, using system native libraries to establish TCP/IP or UDP LDAP connections. |
Pet peeve 😀
src/libraries/System.DirectoryServices.Protocols/src/PACKAGE.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would using be better
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was doubting about that, this makes it quite explicit that you should dispose, and I think the new way of using without {} is not recognizable enough.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Initially supporting only Windows, the assembly now also supports Unix environments, although not yet achieving feature parity between the two. | |
| Supports Windows and Unix, although some features are not supported on Unix. |
Would it be helpful to list some features that aren't available on Unix?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have to rely on the source code and documentation, and they are quite sparse. I found some comments on client and server cert options, added that as suggestion.
|
Thanks @eNeRGy164 |
e44b388 to
cb58bb9
Compare
danmoseley
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me but owner of the area should sign off (and confirm code sample)
|
Feel like doing more of the package readmes? Now you got warmed up 😀 |
|
Oh, whoops 🙂 |
|
@dotnet/area-system-directoryservices please review this package readme PR before EOW so that we can get the change still ported into .NET 8. |
src/libraries/System.DirectoryServices.Protocols/src/PACKAGE.md
Outdated
Show resolved
Hide resolved
buyaa-n
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @eNeRGy164, left a comment, overall LGTM
src/libraries/System.DirectoryServices.Protocols/src/PACKAGE.md
Outdated
Show resolved
Hide resolved
src/libraries/System.DirectoryServices.Protocols/src/PACKAGE.md
Outdated
Show resolved
Hide resolved
cb58bb9 to
2cdb91b
Compare
|
The failure unrelated and doesn't seem actionable. |
Fill out details for the
System.DirectoryServices.ProtocolsNuGet package readme.See #92228