I am trying to install the downloaded code for this book. And, I am new to .NET.

I get the error message about cryptographic failure as below (and tons of others like it) when I try to build the solution in Visual Studio .NET 2003. 106 errors in all. Sounds familiar?

The code is installed under C:\Wrox. I tried building with the original key in the download, as well as a newly generated key using SN -k. Both the keys give the same set of errors.
------------
Cryptographic failure while signing assembly 'C:\Wrox\ThePhile\Modules\Accounts\ACCOUNTSCONFIGU RATION\obj\Debug\Wrox.WebModules.Accounts.Configur ation.dll' -- 'Error reading key file '\Wrox\Keys\ThePhile.snk' -- The system cannot find the path specified. '
------------

As reported by the system, please check that your Key file exist in the following path

"c:\Wrox\Keys\"

Charul Shukla

Indeed, the key file exists as required, C:\Wrox\Keys\ThePhile.snk.

Check that in AssemblyInfo.cs you got the right path like
[assembly: AssemblyKeyFile(@"\Wrox\Keys\ThePhile.snk")]
-Ted

-Ted

Indeed, no problem with AssemblyInfo.cs. The line is unchanged from the downloaded version.

Uday Reddy

After trying various things, I have discovered that the application is looking for the key file at \Wrox\Keys\ThePhile.SNK on the same drive as the installation of Visual Studio. So, what the book says on page 33, viz., that the file should be on "the same physical drive as the project" appears to be false.

What is happening makes sense. If the drive letter is not specified, Visual Studio would look for it on the "current drive," whatever it might be when it got started. So, the book's idea that it will do the right thing if you just omit the drive letter is a bit careless, if you ask me.

Uday Reddy

Well just to give my thought on this is, that for me, it did want the folder to be on the drive of the project, and not on the drive of the installation.

I have 3 partitions, Operating system, application and data, and it did need to be on my data drive not my application drive where VS.net was installed.


Sian Mace

You should NOT use the Wrox keys that come with the source download! It defeats the purpose of a private key if you use somebody else's private key.

There is no requirement to use strongly named assemblies with this project, so you can just comment out those entries in every AssemblyInfo file.

Eric