Skip to content
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

Push Evidence down to System.Security.AccessControl #49411

Merged
merged 2 commits into from
Mar 15, 2021

Conversation

ericstj
Copy link
Member

@ericstj ericstj commented Mar 10, 2021

This can avoid the dependency
System.Security.Cryptography.Xml > System.Security.Permissions (and a slew of other dependencies due to this)

Contributes to #42645

This can avoid the dependency
  System.Security.Cryptography.Xml > System.Security.Permissions
@ericstj ericstj requested review from bartonjs and safern March 10, 2021 03:20
@dotnet-issue-labeler
Copy link

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, to 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.

@ghost
Copy link

ghost commented Mar 10, 2021

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

Issue Details

This can avoid the dependency
System.Security.Cryptography.Xml > System.Security.Permissions (and a slew of other dependencies due to this)

Contributes to #42645

Author: ericstj
Assignees: -
Labels:

area-System.Security, new-api-needs-documentation

Milestone: -

@ericstj
Copy link
Member Author

ericstj commented Mar 10, 2021

/azp run runtime

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@safern safern left a comment

Choose a reason for hiding this comment

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

LGTM.

@ericstj
Copy link
Member Author

ericstj commented Mar 15, 2021

WASM error was fixed with #49492.

@ericstj ericstj merged commit 476f71e into dotnet:main Mar 15, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Apr 14, 2021
@karelz karelz added this to the 6.0.0 milestone May 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants