-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Resolve ILLink warnings in System.Security.Cryptography.Xml #84468
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
Conversation
Note regarding the This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change. |
Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones Issue DetailsFix #73432
|
...braries/Microsoft.Extensions.Configuration.Xml/ref/Microsoft.Extensions.Configuration.Xml.cs
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.
Unfortunate but I think correct. We can also experiment with making XSL APIs safe (i.e. annotating root level APIs as safe but making them pull Xsl.Runtime namespace so that generated code can always access them). In general XSL is required by Signed XML spec so we should look at that independently.
Fix #73432