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

Merge master to dev16.1-preview1 #32218

Merged
36 commits merged into from Jan 8, 2019
Merged

Conversation

dotnet-bot
Copy link
Collaborator

This is an automatically generated pull request from master into dev16.1-preview1.

git fetch --all
git checkout merges/master-to-dev16.1-preview1
git reset --hard upstream/dev16.1-preview1
git merge upstream/master
# Fix merge conflicts
git commit
git push merges/master-to-dev16.1-preview1 --force

Once all conflicts are resolved and all the tests pass, you are free to merge the pull request.

CyrusNajmabadi and others added 30 commits December 19, 2018 12:27
Extract test from AbstractRemoveUnusedMembersDiagnosticAnalyzer for use
in AbstractRemoveUnusedParametersAndValuesDiagnosticAnalyzer via a new
SerializationConstructorCheck utility struct.

Fixes #32133
This API is meant as a file system abstraction that can be mocked /
replaced during testing. Reduced the API to the necessary member and
moved strong name logic to the appropriate type.
Reduced it to the set of methods which reflect the API set. All of the
actual implementation details were moved down to
`DesktopStrongNameProvider`.
The intent is to merge the providers hence having them expose a
capability doesn't make any sense. The code now just infers the mode
based on the arguments and always uses the `DesktopStrongNameProvider`
Big chunk of usage removed with this change. Lots to go though.
Followed up on my questions around the use of `CryptoPublicKey` in
`SourceAssemblySymbol` (both languages). Turns out this does appear to
have a bug in how assembly attributes are processed. Filed #31985 to
follow up on this.
The design of reference assemblies, no matter whether they are generated
using `/ref` or `/refout` is that they are signed if strong signing
would be done for an implementation assembly.

This was implemented correctly for builder based signing but not for COM
based. This PR fixes the signing to be consistent.
Removes the remaining TODO entries in `StrongNameProvider` and cleans up
the structure of the type.
jaredpar and others added 6 commits January 4, 2019 16:59
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Auto-approval

@ghost ghost merged commit 2c5814d into dev16.1-preview1 Jan 8, 2019
@ghost ghost deleted the merges/master-to-dev16.1-preview1 branch January 8, 2019 01:00
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants