Provide strong named assembly

[Alexander Jesner]

Please consider providing NuGet packages with strong named assemblies.

[Nemec]

Is it possible for you to sign it yourself if you're in a situation that needs strong naming? Microsoft suggests that it's not needed in most cases and as we move more toward .NET Core (which doesn't validate strong naming in the first place, afaik) it's even less needed.

Aside from you downloading the project and maintaining a fork w/ strong naming (which I imagine you want to avoid), this blog post suggests you can take the binaries from Nuget's packages folder and strong name them with your own key. This Nuget package claims to include the tools to do that bundled in an easy package.

I don't plan to sign the main package, but if none of the above are usable solutions for you, I can look at what it would take to maintain a separate clipr.StrongName package, as I have seen some libraries do.

[Alexander Jesner]

Thanks for your help.
I will sign the package myself.