versioning is only applied to shared assemblies, not private assemblies?
Reply
![]() |
|
From:
![]() Vishnu-Chivukula
|
Hi Anjali, Versioning can only be applied to shared assemblies not private. Versioning removes the dll hell in .NET. In short u cannot have 2 assemblies of different versions in the local applications bin folder.
This is possible in Shared assemblies by GAC. The magic lies in the way GAC stores the dll's. The GAC folder \Winnt\assembly contains only a shortcut or link to the assembly but not a copy the assembly . Internally under the \winnt\assembly folder, there exists a GAC folder. Inside which GAC creates a folder with the same name as the assembly. Inside this it creates another folder with the version number and the public key of the assembly. So this will ensure that the folder always remains unique. Inside this the .dll file and the .ini files reside. U can view this folder in the command prompt only. By using Windows explorer u cannot view the above directory. Inside the assembly folder, there is a download folder which will contains the downloaded assemblies. This can be viewed through Windows Explorer In private folder u can't have the files with the same name . Otherwise u can use versioning in private path also... |
|
View other groups in this category.
![]() |
To stop getting this e-mail, or change how often it arrives, go to your E-mail Settings.
Need help? If you've forgotten your password, please go to Passport Member Services.
For other questions or feedback, go to our Contact Us page.
If you do not want to receive future e-mail from this MSN group, or if you received this message by mistake, please click the "Remove" link below. On the pre-addressed e-mail message that opens, simply click "Send". Your e-mail address will be deleted from this group's mailing list.
Remove my e-mail address from dotNET User Group Hyd.
|
|