To sign or not to sign the assemblies

[odinserj]

I know that signed assemblies can use only signed dependencies. It the assembly is not signed, then its usage is greatly reduced. But I also heard about some negative aspects of assembly signing, but I don't remember them.

Any ideas?

James Newton-King with his Newtonsoft.Json have such issues, but decided to sign the assembly. ServiceStack guys decided first to not to sign their assemblies, but with 4.0 they supply both signed and unsigned assemblies through different packages. All Microsoft assemblies are signed by default.

[hahmed]

fyi... I remember this issue with the octokit library...

octokit/octokit.net#405

[odinserj]

@hahmed, thanks. It took me about a day to absorb it :) Since I do not believe that anybody needs it (at least yet), I'll postpone this question.

[ses4j]

For the record -- We need it. We are currently ildasm/ilasm'ing each DLL and adding in the public key references ... quite a pain! We're required by our clients to use signed DLLs.