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

Strong Named Assemblies #711

Closed
sys27 opened this issue May 25, 2016 · 3 comments
Closed

Strong Named Assemblies #711

sys27 opened this issue May 25, 2016 · 3 comments

Comments

@sys27
Copy link

sys27 commented May 25, 2016

I have a signed assembly and cannot use yours (Could not load file or assembly 'Squirrel, Version=1.4.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required).

Do you have Strong Named Assemblies or can I sign your dlls with my key?

@anaisbetts
Copy link
Contributor

Sorry, Strong Naming negatively impacts Open Source - I recommend you stop signing assemblies, or as an alternative, I can provide SN binaries for a fee: http://log.paulbetts.org/a-modest-proposal-strong-naming-carbon-offsets/

@joelweiss
Copy link

Try using Strong Namer to sign Squirrel during the build process.

@sjoerd222888
Copy link

@paulcbetts Why does Strong Naming negatively impacts Open Source? I read the discussion on octokit/octokit.net#405 but I fail to get the point I think. Can you please elaborate?

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

4 participants