nuget sign assembly #20

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

Open

ProDInfo opened this issue Mar 20, 2015 · 4 comments

ProDInfo commented Mar 20, 2015

In nuget, the dll is not signed, can yoy update the assembly?
Thanks

Contributor

chillitom commented Mar 20, 2015

reactiveui/ReactiveUI#43 (comment) and http://log.paulbetts.org/a-modest-proposal-strong-naming-carbon-offsets/

Author

ProDInfo commented Mar 20, 2015

I do not agree, sign the assembly ensures the integrity of software.
As I see not intend to generate two packages nuget one signed and one unsigned.

The problem is that downloading the source code'm unable to compile even downloading all dependencies.

I remain unable to use this library

Contributor

chillitom commented Mar 20, 2015

https://www.nuget.org/packages/Nivot.StrongNaming you are welcome to sign it yourself?

Contributor

chillitom commented Mar 20, 2015

Also worth reading: http://www.outercurve.org/blog/2014/03/25/Strongnaming-I-Do-Not-Think-It-Means-What-You-Thin/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment