Wrox Home  
Search P2P Archive for: Go

  Return to Index  

dotnet_windows_app_design thread: Re: dotnet_windows_app_design digest: September 17, 2002


Message #1 by "Barbara Crawford" <b.crawford@v...> on Thu, 19 Sep 2002 20:21:26 -0400
> I have a strong name assembly and I deployed the assembly into Global
> Assembly Cache by using widows installer. But when I try to add a
reference
> to my application the same assembly, the Assembly doesn't display on the
> .NET tab page.
> But the assembly physically present in C:\WINNT\Assembly directory.

The .NET IDE does not use the GAC to locate user assemblies.  In order to
add your
assemblies to the References tab,  a registry hack is required:      If
you're going to do
this, which I don't recommend, create a directory just below the drive (
C:\MyAssemblies, for example).  Copy only production assemblies (throughly
debugged code only) into this directory.
For your own sanity, I would edit my assemblyinfo to give the assembly a
good title, and if
you can manage it, a title that will sort to the top of the list.

Using either regedit or regedt32, navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\AssemblyFolders.
Add a new key and name it the same as your assembly directory
(MyAssemblies);
Edit the default value generated by the previous step so it represents the
fully qualified path
to your assemblies (C:\MyAssemblys).  Save the key and you're good to go.

As always, with any registry hack, you take the risk of making your machine
inoperable.  A good
backup is essential before attempting any registry manipulations of this
kind.

Barbara A Crawford
b.crawford@v...



  Return to Index