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 DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
