GAC solve the problem of DLL HELL?

Posted by Panks under C# on 8/14/2010 | Points: 10 | Views : 17614 | Status : [Member] | Replies : 2
Registering shared DDL in GAC solve the problem of DLL HELL?




Responses

Posted by: Poster on: 8/14/2010 [Member] Starter | Points: 25

Up
0
Down
When you register the shared DLL or DLL in the GAC (global assembly cache), it is available to the whole application hosted on that machine so if you have to use a .dll into two different applications, you do not need to refer that particular dll into both application. Just register that .dll (http://www.dotnetfunda.com/interview/exam2416-what-is-gac-.aspx?isfaq=true) into the GAC and you will be able to refer that .dll in both application.

Registering .dll in many application on the same machine is called DLL HELL now after GAC you do not need to do that so GAC helps solve the DLL HELL problem.

Hope this will help you.

Panks, if this helps please login to Mark As Answer. | Alert Moderator

Posted by: Abhi2434 on: 8/15/2010 [Member] [Microsoft_MVP] [MVP] Silver | Points: 25

Up
0
Down
GAC helps in the problem of DLL hell. Dll hell is produced when there is Version conflict. Say you have installed Adobe Premier 5 and also Adobe Photoshop 7. Or you want both Photoshop 7 and Photoshop CS to run side by side in the same machine. In case of COM, once a DLL is registered, if you want to register a new version of it, you need to unregister the previous dll and then register the new one. This makes cumbersome and hence DLL hell arises where the older version ceases to execute when new version is installed.

In GAC, assemblies holds everything. The header contains the metadata, and hence you can store more than 1 version of the same dll side by side and it will work correctly. Hence GAC/ .NET solves the problem of DLL hell

www.abhisheksur.com

Panks, if this helps please login to Mark As Answer. | Alert Moderator

Login to post response