#1
|
|||
|
|||
"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? |
#2
|
|||
|
|||
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.
|
#3
|
|||
|
|||
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. |
#4
|
|||
|
|||
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.
|
#5
|
|||
|
|||
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! |
#6
|
|||
|
|||
Do you need to set the "Start in:" field in the run step to specify the current directory?
|
#7
|
|||
|
|||
I'm using a Make VS.NET step, not a Run Program. There is no "Start in" option.
|
#8
|
|||
|
|||
Along the same lines, you could try a Set Current Dir step, setting the current dir appropriately (prior to the Make VS.NET step).
|
#9
|
|||
|
|||
Hey, that worked! Thanks, pjaquiery and kevina!
|
|
|