Skip to content

Conversation

carlossanlop
Copy link
Contributor

Ported with DocsPortingTool.

@gewarren targeting the net6-rc1 branch.

@carlossanlop carlossanlop added the area-System.Security Issues related to security practices for .NET developers. label Sep 3, 2021
@carlossanlop carlossanlop self-assigned this Sep 3, 2021
@ghost
Copy link

ghost commented Sep 3, 2021

Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @GrabYourPitchforks
See info in area-owners.md if you want to be subscribed.

Issue Details

Ported with DocsPortingTool.

@gewarren targeting the net6-rc1 branch.

Author: carlossanlop
Assignees: carlossanlop
Labels:

area-System.Security

Milestone: -

<param name="strUri">The Uniform Resource Identifier (URI) of the information to be referenced by the new instance of <see cref="T:System.Security.Cryptography.Xml.KeyInfoRetrievalMethod" />.</param>
<param name="typeName">The URI that describes the type of data to retrieve.</param>
<param name="strType">To be added.</param>
<param name="strType">The URI that describes the type of data to retrieve.</param>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bartonjs @GrabYourPitchforks this was detected by DocsPortingTool as an argument that got renamed, and had to manually choose which was the old argument name. I am not entirely sure if strType was typeName or strUri, but it made more sense to me to choose the description from typeName. Was this the right choice?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's called typeName in both .NET Framework and .NET (nee Core), for some reason it was strType in Xamarin.

@gewarren

This comment has been minimized.

carlossanlop and others added 2 commits September 8, 2021 12:35
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
…xception.xml

Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
@opbld31

This comment has been minimized.

Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
@opbld31
Copy link

opbld31 commented Sep 8, 2021

Docs Build status updates of commit 6ecd4bd:

✅ Validation status: passed

File Status Preview URL Details
xml/System.Security.Cryptography.Xml/CipherReference.xml ✅Succeeded View
xml/System.Security.Cryptography.Xml/CryptoSignedXmlRecursionException.xml ✅Succeeded View
xml/System.Security.Cryptography.Xml/DataReference.xml ✅Succeeded View
xml/System.Security.Cryptography.Xml/EncryptedReference.xml ✅Succeeded View
xml/System.Security.Cryptography.Xml/EncryptedXml.xml ✅Succeeded View
xml/System.Security.Cryptography.Xml/EncryptionMethod.xml ✅Succeeded View
xml/System.Security.Cryptography.Xml/EncryptionProperty.xml ✅Succeeded View
xml/System.Security.Cryptography.Xml/KeyInfoEncryptedKey.xml ✅Succeeded View
xml/System.Security.Cryptography.Xml/KeyInfoRetrievalMethod.xml ✅Succeeded View
xml/System.Security.Cryptography.Xml/KeyReference.xml ✅Succeeded View

For 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:

@carlossanlop carlossanlop merged commit 05641e7 into dotnet:net6-rc1 Sep 8, 2021
@carlossanlop carlossanlop deleted the upd.sec.cryp.xml branch September 8, 2021 22:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-System.Security Issues related to security practices for .NET developers.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants