Pedro Lamas • 3/1/2016

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

Read Original

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
Still Strong-Naming your Assemblies? You do know it's 2016, right?

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
Quoting Thariq Shihipar
Simon Willison • 2 votes
2
Top picks — 2026 January
Paweł Grzybek • 1 votes
3
In Praise of –dry-run
Henrik Warne • 1 votes
4
Deep Learning is Powerful Because It Makes Hard Things Easy - Reflections 10 Years On
Ferenc Huszár • 1 votes
5
Vibe coding your first iOS app
William Denniss • 1 votes
6
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
7
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes