Strong naming

GongSolutions.WPF.DragDrop is now strong-named again (beginning with v2.0).

Why?

The author of the (in)famous "Still strong naming your assemblies?" blog article has now done an about-face and now advocates strong-naming your assemblies again in an update to that same blog post:

Though the information and concerns in this blog post are still very true, I’ve actually had a change of heart and I’m now advocating to Start Strong-Naming your Assemblies!!

Start Strong-Naming your Assemblies!

Microsoft's corefx team also now strong-names and while they say not every assembly needs it, it's still useful: https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/strong-name-signing.md

GongSolutions.WPF.DragDrop is not strong-named (beginning with v1.0).

Why?

Strong-named assemblies are only useful in some rare scenarios. If you need strong-named assembly then you can compile the source by yourself ore use the Strong Namer from Daniel Plaisted @dsplaisted or Strong-Name Signer from Werner van Deventer @brutaldev.

More informations about the reason of this decision can be found here:

• Still Strong-Naming your Assemblies? You do know it’s 2016, right?
• XAML Behaviors UWP Managed 1.1.0
• Strong-Named Assemblies