Resolve ILLink warnings in System.Security.Cryptography.Xml#84468
Resolve ILLink warnings in System.Security.Cryptography.Xml#84468eerhardt merged 3 commits intodotnet:mainfrom
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
krwq
left a comment
There was a problem hiding this comment.
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