enable strong naming for better .NET Framework support #8
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
|
Thanks for the work 🙂. At first glance, looks great. |
|
I haven't forgotten about this. It's been a few months since I've last published, so I'm doing things like updating nuget packages, adding support for net8 (unit tests are failing due to changed behavior), dropping support for deprecated frameworks, etc. Hopefully I'll have this added by the end of the week. I suppose in the meantime, you can reference your own build. |
|
Sounds good, thanks! |
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.
Enabling strong naming allows this library to be referenced by strong named .NET Framework projects.
Key was created using
sn -k StrongNamedAssemblyKey.snk.