Kinook Software Forums

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

Reply
 
Thread Tools Rating: Thread Rating: 23 votes, 5.00 average. Display Modes
  #1  
Old 12-02-2004, 09:35 AM
CRogers CRogers is online now
Registered User
 
Join Date: 07-02-2003
Posts: 6
Unhappy "Error reading key file" when compiling VS.NET web app

I have a web app whose assembly is strongly named. Compilation within VS.NET works fine. Compiling during a build fails with the error

vbc : error BC30140: Error creating assembly manifest: Error reading key file 'path\to\my.snk' -- The system cannot find the path specified.

Compiling non-web apps using this same key file works fine as well.

Any advice?
Reply With Quote
  #2  
Old 12-02-2004, 10:48 AM
CRogers CRogers is online now
Registered User
 
Join Date: 07-02-2003
Posts: 6
Follow-up: The <Assembly: AssemblyKeyFile("...")> property in my AssemblyInfo.vb file had been using a relative pathname to the key file. I just discovered that if I use an absolute pathname, the build can handle it. However, this isn't an ideal solution, as it removes some amount of location-independence from my project.
Reply With Quote
  #3  
Old 12-02-2004, 11:19 AM
kevina kevina is online now
Registered User
 
Join Date: 03-27-2003
Posts: 825
If you show the command-line used by Visual Build Professional, then execute this same command-line call manually, does the error still occur?
It sounds like the Microsoft command-line compiler (devenv.com) is not accepting the relative path.
Reply With Quote
  #4  
Old 12-02-2004, 02:33 PM
CRogers CRogers is online now
Registered User
 
Join Date: 07-02-2003
Posts: 6
Yes, the error still occurs when executing the command-line call manually. I'm not sure why this would make a difference, though. There's no parameter within that command line that set the key pathname. That property is statically defined in AssemblyInfo.vb within the project.
Reply With Quote
  #5  
Old 12-02-2004, 02:37 PM
CRogers CRogers is online now
Registered User
 
Join Date: 07-02-2003
Posts: 6
Oh, but now I see the point you're making. This is not a builder issue; this is purely a VS.NET issue.

So, never mind as far as this forum is concerned. Thanks for your help!
Reply With Quote
  #6  
Old 12-02-2004, 02:45 PM
pjaquiery pjaquiery is online now
Registered User
 
Join Date: 01-20-2003
Location: Dunedin, New Zealand
Posts: 114
Do you need to set the "Start in:" field in the run step to specify the current directory?
Reply With Quote
  #7  
Old 12-02-2004, 03:02 PM
CRogers CRogers is online now
Registered User
 
Join Date: 07-02-2003
Posts: 6
I'm using a Make VS.NET step, not a Run Program. There is no "Start in" option.
Reply With Quote
  #8  
Old 12-02-2004, 03:15 PM
kevina kevina is online now
Registered User
 
Join Date: 03-27-2003
Posts: 825
Along the same lines, you could try a Set Current Dir step, setting the current dir appropriately (prior to the Make VS.NET step).
Reply With Quote
  #9  
Old 12-02-2004, 03:37 PM
CRogers CRogers is online now
Registered User
 
Join Date: 07-02-2003
Posts: 6
Thumbs up

Hey, that worked! Thanks, pjaquiery and kevina!
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 05:24 AM.


Copyright 1999-2019 Kinook Software, Inc.