Update x500DistinguishedName snippets to include relevant code #7328
Conversation
dotnet-issue-labeler
bot
added
the
area-System.Security
|
Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @GrabYourPitchforks Issue DetailsSummaryAdds x500DistinguishedNameFlag example to the general x500DistinguishedName snippets making the snippet more relevant to the X500DistinguishedNameFlags documentation page. Fixes #7327
|
|
|
|
Docs Build status updates of commit d38e40c: ✅ Validation status: passedFor more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
|
Just a two-cents opinion from an end-user who discovered this issue whilst looking at the documentation for What would be useful is if the documentation indicated whether using the enum affected how the input string was parsed or validated, or just set some property of the resulting For instance, one of the flags values is If the example code instead used some literal input strings, and described the resulting output, e.g. something of the form... ...(but accurate), that might be more demonstrative of this enum. |
|
Learn Build status updates of commit ddc8a3b: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Summary
Adds x500DistinguishedNameFlag example to the general x500DistinguishedName snippets making the snippet more relevant to the X500DistinguishedNameFlags documentation page.
Fixes #7327