Still Strong-Naming your Assemblies? You do know it's 2016, right?
Read OriginalThis 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
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
Webinar Series – SQL Server Indexing
Koen Verbeeck
•
2 votes
2
Risks and Limitations of AI in the Life Sciences
Jeremy Howard
•
2 votes
3
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane
•
2 votes
4
1M context is now generally available for Opus 4.6 and Sonnet 4.6
Simon Willison
•
1 votes
5
AI is my CMS
Chris Coyier
•
1 votes
6
LLM Use in the Python Source Code
Miguel Grinberg
•
1 votes