Pedro Lamas • 3/1/2016

Still Strong-Naming your Assemblies? You do know it's 2016, right?

This article examines the history and drawbacks of strong-naming .NET assemblies. It argues that while strong-naming was useful for enterprise features in the past, it creates significant problems for third-party library developers, especially with platforms like Silverlight and Windows Phone that lack assembly binding redirection. The author initially advises against strong-naming but notes a later change of heart in an update.

0 comments

#.net #versioning #Nuget