DLL Hell problem

Hi jon,

DLL Hell refers to the set of problems caused when multiple applications attempt to share a common component like a dynamic link library (DLL) or a Component Object Model (COM) class. The reason for this issue was that the version information about the different components of an application was not recorded by the system.


How to solve this DLL Hell Problem?

. 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.

Thanks

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Farukh Mujawar15y ago

Dear Jon,
              Windows Registry can not support the multiple versions of  same com component this is called the dll hell problem.                 Dll hell problem is solved by dotnet it allows the  application to specify not only the library it needs to run but also the version of the assembly

Satyapriya Nayak15y ago
Hi jon,

DLL Hell refers to the set of problems caused when multiple applications attempt to share a common component like a dynamic link library (DLL) or a Component Object Model (COM) class. The reason for this issue was that the version information about the different components of an application was not recorded by the system.
```
How to solve this DLL Hell Problem? 
```
. 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.

Thanks