Strong named assembly

Sep 22, 2011 at 2:27 PM

Can you sign your assemblies by some key?

Some projects with strong named assembly can't include "weak" named libraries - so every time after version update have to recompile SuperWebSocket and SuperSocket assembly with signing

Sep 22, 2011 at 2:36 PM

Ok, I'll think about it!

Sep 25, 2011 at 3:49 PM
Edited Sep 25, 2011 at 3:50 PM

Before you go ahead and strong name the assemblies, you should read The assembly strong naming conundrum discussion between the NuGet developers.

If possible, you should consider modifying the build script to output signed and unsigned versions.

Sep 25, 2011 at 3:58 PM

Thank you very much!

Dec 18, 2011 at 2:24 PM

Hi, kerryjiang!

Have you planned anything on this problem? 

P.S. thanks for your work

Dec 27, 2011 at 9:34 AM

I have added strongly named assembly output for SuperWebSocket, please run Build.bat, the signed assemblies will be generated in the folder "bin".