Strong name the assembly?

[ScottHutchinson]

Would it be a good idea to strong name the assembly included in the Nuget package, so all the consumers who have a strong-named project don't have to do it?

[ScottHutchinson]

See Why strong-name your assemblies?. "If you are an open-source developer and you want the identity benefits of a strong-named assembly for better compatibility with .NET Framework, consider checking in the private key associated with an assembly to your source control system."

I don't feel "strongly" about this. (Pun intended)

[ScottHutchinson]

Sadly, I've decided not to use this package, because it's too hard to use from a strong-named project. See dsplaisted/strongnamer#64.