Article ID: 324168 - View products that this article applies to.
This article was previously published under Q324168
This step-by-step article describes how to deploy an assembly to the global assembly cache of the target computer. This makes the target computer shareable in other applications. When you do this, strong name signatures must be verified only one time. Also, by loading an assembly from the same location on the disk, you take advantage of the code sharing behavior that the operating system provides and the working set improves.
Step by step procedureUse Visual Studio .NET to create a setup project, and then deploy the assembly to the target computer global assembly cache. To do this, follow these steps:
RemarksIf you rebuild the assembly later, and you change its Version Minor but you do not change its Public Key Token, the relating strong name will be different. Because of this, if you follow steps 1 through 4 to deploy other applications that reference to the rebuilt assembly (which is contained in the package), the target global assembly cache will contain both assemblies.
If the assembly is already strong-named, you can deploy another application in the target global assembly cache. If the assembly is not strong-named, you receive the following message from Task List:
Assembly AssemblyName must have a shared name to be installed globally
For more information about assemblies and the global assembly cache, visit the following Microsoft Web sites:
Global Assembly Cache
Simplifying Deployment and Solving DLL Hell with the .NET FrameworkFor more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/315682/ )How to install an assembly into the global assembly cache in Visual Studio .NET
Article ID: 324168 - Last Review: December 3, 2007 - Revision: 3.7