Hacker News new | ask | show | jobs
by moron4hire 2324 days ago
DLL Hell had nothing to do with project development. It was a problem of application deployment and running applications with DLLs in shared locations.

https://en.wikipedia.org/wiki/DLL_Hell

  The problem arises when the version of the DLL on the computer is different than the version that was used when the program was being created.
Other than the GAC, which was never recommended for use anyway, .NET has never had DLL Hell
1 comments
pjmlp 2324 days ago
GAC was surely the recommended way until .NET 4.0, when the location changed.
link
moron4hire 2324 days ago
No, the recommended way was to install your application with all dependency DLLs in the application install location.

And I've misspoken about GAC causing DLL Hell for .NET. It fixed DLL Hell, but introduced a new Strong Naming Hell.

link
pjmlp 2324 days ago
Initially that recommendation only applied to native code DLLs, not managed ones, as far as I can remember.
link