1

Closed

Sign Assemblies

description

The assemblies from NuGet aren't strong-named, thus they cannot be referenced by projects that build strong-named assemblies.

In my case, I'm going to have to re-compile the source code myself so that I can strong name the MapControl.WPF.dll and ImageFileCache.dll assemblies; however, I won't be able to get any future updates through NuGet. I'll have to rebuild the source again each time a new version is released.

Please sign your assemblies!

Thanks for a great tool.
Closed Oct 31, 2013 at 4:05 PM by ClemensF
I'll think about it.

comments

davedev wrote Oct 31, 2013 at 4:50 PM

Thanks, I appreciate it, but what exactly is stopping you from merging my pull request? I see no downside to signing your assemblies. If you don't sign them, then deploying on NuGet is useless to many people. My pull request simply adds an .snk file to the solution and configures all library projects to be signed. This shouldn't cause you any trouble going forward.

Maybe I can clear up any confusion you may have about strong-naming. Let me know if you have any questions. Here's some related documentation about the benefits:

http://msdn.microsoft.com/en-us/library/wd40t7ad.aspx

Also, please leave the work item open so that others can vote it up!

ClemensF wrote Oct 31, 2013 at 7:45 PM

Sorry, but I won't leave the item open, as any votes wouldn't influence how I deal with the issue. I'll provide either strong-naming only or also signing with the next release.