Kinook Software Forum

Go Back   Kinook Software Forum > Visual Build Professional > [VBP] Third Party Tools

Reply
 
Thread Tools Rate Thread Display Modes
  #1  
Old 02-10-2004, 10:06 AM
shafjac shafjac is online now
Registered User
 
Join Date: 02-04-2004
Posts: 8
Question GAC Install Partial failure

I'm encountering a weird error when attempting to perform a GAC Install step via Visual Build Pro. I'm attempting to install an assembly to the GAC, and then "Update AssemblyFolders registry key" (the value I have for that textbox is DeluxeLog.LogReader). The output for this step is as follows:

Code:
Building project step 'Install LogReader library to the Global Assembly Cache'...
"C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\bin\gacutil.exe" /nologo /if "c:\development_current\Common\Lib\LogReader\bin\Release\LogReader.dll"
Assembly successfully added to the cache
The system cannot find the file specified.
Step 'Install LogReader library to the Global Assembly Cache' failed
So it seems that the assembly gets installed to the cache just fine, but the registry part is failing (in fact, if I remove the registry key text, it works just fine). The odd thing is that this works fine on my local machine, but not on my build machine. I'm not sure if it's a configuration setting or what. What file is it trying to find?

Any ideas?

Also, I apologize if this has already been covered, I can't seem to force the forum software to search for "GAC" -- it requires a minimum of 4 letters, and nothing pertinent came up for "global assembly cache".

Thanks in advance for any help.
Reply With Quote
  #2  
Old 02-10-2004, 11:32 AM
kinook kinook is online now
Administrator
 
Join Date: 03-06-2001
Location: Colorado
Posts: 6,003
From the GAC Install help topic:

Update AssemblyFolders registry key: If a folder name is specified in this field, a registry key by that name is create/updated or removed from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramewor k\AssemblyFolders and its default entry set to the path of the assembly file.


Apparently that registry key does not exist on the box this is failing on.
Reply With Quote
  #3  
Old 02-10-2004, 11:34 AM
shafjac shafjac is online now
Registered User
 
Join Date: 02-04-2004
Posts: 8
Quote:
Originally posted by kinook
From the GAC Install help topic:

Update AssemblyFolders registry key: If a folder name is specified in this field, a registry key by that name is create/updated or removed from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramewor k\AssemblyFolders and its default entry set to the path of the assembly file.


Apparently that registry key does not exist on the box this is failing on.
Okay, but shouldn't the GAC Install create the registry key if it's not there?
Reply With Quote
  #4  
Old 02-10-2004, 02:30 PM
kevina kevina is online now
Registered User
 
Join Date: 03-26-2003
Posts: 825
It probably should and we will add that request to the list of issues/enhancements to address in a future release of Visual Build Pro.

Our developers made the assumption that this default value was created during a normal .NET FrameSDK and/or VS.NET install, which must not ALWAYS be the case.

For now if you manually create this default value under the registry key specified earlier in the thread, everything should work on your build machine.

If you want this to be automated, add a Write Registry step (before the GAC Install step) that ensures this default value exists (it will create the key if missing)...

Kevin
Reply With Quote
  #5  
Old 02-11-2004, 09:19 AM
shafjac shafjac is online now
Registered User
 
Join Date: 02-04-2004
Posts: 8
Ah, okay. For a minute there I thought you were saying the DeluxeLog.LogReader subkey didn't exist so the GAC Install failed.

But evidently you meant that the AssemblyFolders key wasn't there and therefore the attempt to create the DeluxeLog.LogReader subkey failed. And you're right -- that AssemblyFolders key wasn't on that machine. I would have assumed the same thing you did -- that key should be created by default, but I guess not in every case.

Anyway, I created that key and the build works fine now.

If it's any help to you, that machine is running a pretty fresh install of Windows 2003 Server Enterprise Edition. I'm pretty sure that comes pre-installed with the .NET framework.

Thanks for the help.
Reply With Quote
Reply

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 09:33 PM.


Copyright © 1999-2023 Kinook Software, Inc.