Thank you Ken. That's my current workaround solution. I was expecting that
when I right click on "References" and click to add a reference, the
abcLib.dll would show up as a choice under the .NET tab just like other
system dlls show up there but it doesn't. Would you, or anyone else, know if
that is normal for a dll in GAC to not show up as a choice in the list of
dlls when adding a reference to a project? If that is true then how do you
actually make it show up there?
It just sounds counterintuitive that even if you have something in your GAC
you have to have its local copy to build a project that needs that dll. I
would expect it to behave like any other system dll.
Thanks for your thoughts and feedback.
> You might want to get a copy of the DLL and put it somewhere outside the
> for reference purposes at compile time. (Drop it into the /bin folder and
> Reference to it in VS.NET.)
> At runtime, the application will go to the version in the GAC first.
> I have created an abcLib.dll file that has common functions I want to use
> across my projects. I created a key file using sn.exe, complied the
> using the key and installed the dll in global assembly using gacutil.exe
> abcLib.dll. The file shows up under Winnt\assembly folder with key and
> version. However when I try to use that from a codebehind page the Imports
> statement does not show that library as a completion choice. If I go ahead
> and add "Imports abcLib" anyways, the complier complains that it does not
> know what that is referring to.
> What step am I missing from being able to use that dll from GAC in my
> Thanks for your help.