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.

Sign up for GitHub

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

Jump to bottom

Strong name the library #39

Closed
mattjohnsonpint opened this issue Mar 17, 2019 · 0 comments
Closed

Strong name the library #39

mattjohnsonpint opened this issue Mar 17, 2019 · 0 comments

Comments

@mattjohnsonpint
Copy link
Owner

The guidance from the .NET team has changed, and is now clear that OSS libraries should be strong named.

https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming

This will be a breaking change
https://haacked.com/archive/2012/02/16/changing-a-strong-name-is-a-major-breaking-change.aspx/

Addresses previous request #25
mattjohnsonpint added a commit that referenced this issue Jun 14, 2019
@mattjohnsonpint
Use an SNK (fixes #39)
dd464c2
mattjohnsonpint added a commit that referenced this issue Jun 14, 2019
@mattjohnsonpint
Use an SNK (fixes #39)
781101c
mattjohnsonpint added a commit that referenced this issue Jun 18, 2019
@mattjohnsonpint
Use an SNK (fixes #39)
4a51a8f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mattjohnsonpint