how dll hell problem solve in dotnet

Question

Sivasankar Gorantla · Answer

Hi Hamid, Let me first explain you what is DLL hell then we will discuss the resolution to it. DLL hell : DLL hell is a term used by many developers which states that "the alteration of a DLL file by a program, negatively affects the functionality of another program which is referring same DLL. Resolution: Applications must be self-describing. Applications that are self-describing remove the dependency on the registry, enabling zero-impact installation and simplifying uninstall and replication. Version information must be recorded and enforced. Versioning support must be built into the platform to ensure that the proper version of a dependency gets loaded at run time. Must remember "last known good." When an application successfully runs, the platform must remember the set of components—including their versions—that worked together. In addition, tools must be provided that allow administrators to easily revert applications to this "last known good" state. Support for side-by-side components. Allowing multiple versions of a component to be installed and running on the machine simultaneously allows callers to specify which version they'd like to load instead of a version "forced" on unknowingly. The .NET Framework takes side by side a step farther by allowing multiple versions of the framework itself to coexist on a single machine. This dramatically simplifies the upgrade story, because an administrator can choose to run different applications on different versions of the .NET Framework if required. Application isolation. The .NET Framework must make it easy, and in fact the default, to write applications that cannot be affected by changes made to the machine on behalf of other applications. Please let me know if have any further questions on this. Thanks, Siva

Prasham Sabadra · Answer

Hi, Please have a look once following URLs: https://msdn.microsoft.com/en-us/library/ms973843.aspx?f=255&MSPPError=-2147217396 https://social.msdn.microsoft.com/Forums/vstudio/en-US/97b4aa67-80a1-41ed-b00e-60e8bb952eea/how-net-solve-dll-hell-problem?forum=netfxbcl

Manikandan Murugesan · Answer

Refer the following link to get the solution : http://www.c-sharpcorner.com/blogs/dll-hell-problem-and-solution1 Dll Hell refers to a set of problems caused when multiple applications attempt to share a common component like a dynamic link library (DLL). The reason for this issue was that the version information about the different components of an application was not recorded by the system. .Net Framework provides operating systems with a Global Assembly Cache. This Cache is a repository for all the .Net components that are shared globally on a particular machine. When a .Net component 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. The component is then registered in the repository and indexed by its strong name, so there is no confusion between different versions of the same component, or DLL.