nuget libraries unsigned

[btarb24]

Can the libraries please be signed before being published to nuget? Leaving them unsigned adds a requirement that consumers need to add pre-build steps to sign the libraries. This effort needs duplicated for each framework being used.

[StevenBonePgh]

I think this is a good time to consider this. Microsoft just released their new Open-source library guidance and advise strong naming. This is one of a ever-smaller handful of libraries I use that prevent me from strong-naming portions of my code (the option to sign an external library on build exists, but that is conceptually broken for many reasons). EasyNetQ has resisted this also for a long time as well and they are finally relenting...

[jmh76]

:+1: I had to clone and build from source, but I'd much rather get strong named assemblies in a nuget package.

[statianzo]

If anyone can give a PR that does signing during the Appveyor build, I'm fine with bringing it in.