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

Missing strong name #18

Closed
B-Virtual opened this issue Dec 13, 2016 · 2 comments
Closed

Missing strong name #18

B-Virtual opened this issue Dec 13, 2016 · 2 comments
Assignees

Comments

@B-Virtual
Copy link

Hi,

Would it be possible to strongly sign your release version that you package in your Nuget Package. This way the nuget can also be used in projects that require all assemblies to be signed. Make sure you make a wise decision on your key because if you change it in future versions other issues come up for backwards compatibility.

Kind regards,
Bjorn

@thepirat000
Copy link
Owner

thepirat000 commented Dec 13, 2016

Will probably work on this soon, but will provide different NuGet packages for Strongly Named versions.
See this blog post

Using StrongNamer could be a temporary workaround.

@thepirat000
Copy link
Owner

thepirat000 commented Dec 17, 2016

For compatibility, I've created a Strong Name version of each package (except for Audit.NET.MongoDB since the MongoDB driver is not signed).

Use the new packages ending with ".StrongName":

Audit.NET.StrongName
Audit.NET.AzureDocumentDB.StrongName
Audit.NET.AzureStorage.StrongName
Audit.NET.SqlServer.StrongName
Audit.EntityFramework.StrongName
Audit.DynamicProxy.StrongName
Audit.Mvc.StrongName
Audit.Wcf.StrongName
Audit.WebApi.StrongName

@thepirat000 thepirat000 self-assigned this Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants