..and I'll add for Ragnvald that the GAC is a deployment choice, not a repository for assemblies you want to reference at development time. It doesn't matter where the referenced assembly is at build time because at run-time it goes through this sequence to find them.
http://msdn2.microsoft.com/en-us/library/yx7xezcf.aspx Phil Wilson -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Vince P Sent: Thursday, December 01, 2005 7:07 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Gacutil problems Having an assembly be in the GAC doesn't mean it will show up in the .Net References dialog.. In fact there is no link between them. The dialog is working off a list of file system paths. This was my first major "mistake" when working in .Net. I wanted the convenience of being able to reference some utility assemblies from any project I wanted.. So I went the GAC route... Well the GAC was really a big waste of time. (and the GAC introduces more problems than it solved , at least for my needs) I'm content to let MS have the GAC and major UI component authors. By claiming God As his holy right | He's stealing a God From the Israelites Stealing a God From the Muslim too | There is only one God Through and through - "John the Revelator" - Depeche Mode -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Ragnvald Barth Sent: Thursday, December 01, 2005 4:50 AM To: [email protected] Subject: [ADVANCED-DOTNET] Gacutil problems I have a .net 2.0 dll that will be used from several different applications. So I figured I should put the dll in the gac. I am using Visual Studio 2005 Team Suite release candidate for this project. First I typed gacutil /i MyDll.dll in the .net 2005 command prompt. It worked ok. Then I added the gacing as a post build step. Because I didnt have the directory of gacutil in my path I added the post build step like this: C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe /i MyDll.dll It worked fine too. Then I added C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin to my path, and changed the post build step to: gacutil /i MyDll.dll When I tried to build I got the error code 9009. I have tried to google for gacutil 9009 and found others with the same problem, but no one has a solution. Is this a gacutil bug or am I doing something wrong? Then I went back to using gacutil /i MyDll.dll from the 2005 command prompt, and manually gaced my dll successfully, because I wanted to use it from another solution. In the other solution, I went to "add reference..." on a project, and tried to find my MyDll in the .NET tab. But it is not there! Why? Where can I find it? What am I doing wrong? =================================== This list is hosted by DevelopMentorR http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
