Strong-name the assemblies #9
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dfederm
force-pushed
the
strong-naming
branch
from
f6b210a
to
c80c3e7
Compare
|
@ThomasPiskol since you have maintainer access now (yay!), mind taking a look? My hope is to get this merged, pushed to NuGet.org, and integrated downstream by EOW :) |
ThomasPiskol
approved these changes
Jan 12, 2022
I'll integrate the changes in my PR, so let's see if we can let your wish come true 🙂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #8
I generated the snk file simply by running
sn -k StrongName.snk.I also added a pretty basic
Directory.Build.propsandDirectory.Build.rsp