Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


Tip of the Day
Language: VB7
Expertise: Intermediate
Jul 20, 2002

Understanding VS.NET public and private assemblies

As you might have noticed, the Add Reference dialog in Visual Studio displays all the assemblies in the GAC, which brings up the following question: is there a way to have this list display assemblies that aren't in the GAC? The answer is yes, and the technique couldn't be easier.

Use the REGEDIT utility to browse the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.0\AssemblyFolders\ _
    PublicAssemblies
This key has a value that contains a path to a directory, for example:
C:\Program Files\Microsoft Visual Studio .NET\Common7\IDE\PublicAssemblies
It turns out that all the assemblies deployed in this directory appear in the Add Reference and the Object Browser's Component Selector dialog box. These assemblies typically run inside the environment and are called by macros, add-ins, or user code. For example, this directory contains the extensibility.dll and VSlangProj.dll, which are wrappers around COM objects and that are used to create add-ins.

If you have assemblies that should run inside the environment but shouldn't appear in the above dialog boxes and aren't called by user code, you can deploy to another directory named PrivateAssemblies, for example:

C:\Program Files\Microsoft Visual Studio .NET\Common7\IDE\PrivateAssemblies
Francesco Balena
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date