DLL Hell problem in .NET
How's the DLL Hell problem solved in .NET?
Know the answer? Post it — somebody with the same question will find it here.
Sign in to answer this question
It is the same account you read, post and publish with — and you will come straight back to this page.
Ajitender VijayPosted Jan 27, 2012, 12:47 AM
Global assembly Cache (GAC) is a repository for all the .Net components/dll that are shared globally on a particular machine. When a .Net component/dll is installed onto the machine, the Global Assembly Cache looks at its version, its public key, and its language information and creates a strong name for the component/dll. The component/dll is then registered in the GAC and indexed by its strong name, so that even with same name of assembly could be install to GAC that will be having two different versions. Once versioning done with any assembly there will be no chance to conflict, which was earlier happening (DLL HELL).
below links contain great explanation to your question.
http://venkataspinterview.blogspot.com/2011/05/what-is-dll-hell-in-net.html
http://venkataspinterview.blogspot.com/2011/06/how-is-dll-hell-problem-solved-in-net.html
thanks
Satyapriya NayakPosted Jan 27, 2012, 12:44 AM
The dll hell problem is solved in .NET by signing the shared assemblies with strong name.
Please refer the below link
http://venkataspinterview.blogspot.com/2011/06/how-is-dll-hell-problem-solved-in-net.html
Thanks