sabir

• Jan 12th, 2006

 

as we knoe that in .net we can use the conecpt of assembly .assembly we r devieding it to two types 1)private assembly and the sharedassembly in case of assembly we r going   store it the gac folder and here we r going to specify the verrsion number since it is requird us to resister into  the registery  it into the like this we r over comming the dllhell

Amit

• Apr 24th, 2006

 

Unlike VB6; .net does not require to generate GUID for the dll's. The dll's are hosted thru applications ,IIS or windows services. These things internally refer to the physical locations of the file thus even if the dll is updated with certain functionalities the older application can still refer to the previous version of the Dll. and so the Hell is now a heaven..... :)

jyothibasa

 Profile Answers by jyothibasa 

• Oct 18th, 2006

 

DLL HELL IS NOTHING BUT VERSIONING PROBLEM IN .NET ...............

BEFORE .NET COM COMPONENTS ARE USED,BUT THEY WILL HAV SOME PROBLEM WITH VERSIONS , IF CLIENT APPLICATIONS IS HAVING A COM COMPONENT WITH 1.0 VERSION AND NOW SUPPOSE THAT VERSION HAS BEEN CHANGED THEN , IT WILL EFFECT THE CLIENT APPLICATION USING OLD VERSION .........COZ.....THE NEW VERSION OF COM COMPONENT REPLACES THE OLD VERSION................

THIS PROBLEM IS OVERCOME IN .NET USING ASSEMBLIES IE .DLL FILES......

GAC(GLOBAL ASSEMBLY CACHE) CAN HAV THE ASSEMBLIES OF TWO VERSIONS WITH SAME NAME......

THE NEWER VERSION OF ASSEMBLY CANT REPLACE THE OLDER VERSION .....

SO THERE IS NO PROBLEM FOR THE CLIENT APPLICATION WHICH USES THE OLDER VERSION ..............

IF WE WANT TO CHANE THE CLIENT APPLICATION FROM USING OLDER VERSION TO NEWER VERSION WE CAN GO FOR "CONFIGURATION SETTINGS".......