Hello,

I am new to .NET. I think I am having "KEY" problem here. In the AssemblyInfo.cs file in each individual project, I need to change the key path to absolute physical path of the SNK file to compile(I:\wrox\keys\ThePhile.snk for example). And those individual projects compile fine. But in project "ThePhile", I got "Cryptographic failure while signing assembly 'D:\Documents and Settings\administrator\VSWebCache\...\ThePhile\obj \Debug\ThePhile.dll' -- 'Error reading key file '\Wrox\Keys\ThePhile.snk' -- The system cannot find the path specified. '" error when I compiled. If my folder structure is: I:\wrox\ThePhile, how should I specify the path? The original code simply does not work, I have to change it to something.

Btw, my operating system and .NET framework was installed on 2 different physical hard drives.

Another question is: the book used .NET 1.0, I am having .NET 2003 installed, does it work on v1.1?

Thanks for any help.

I figured it out..

Hello,

I am new to .NET. I think I am having "KEY" problem here. In the AssemblyInfo.cs file in each individual project, I need to change the key path to absolute physical path of the SNK file to compile(I:\wrox\keys\ThePhile.snk for example). And those individual projects compile fine. But in project "ThePhile", I got "Cryptographic failure while signing assembly 'D:\Documents and Settings\administrator\VSWebCache\...\ThePhile\obj \Debug\ThePhile.dll' -- 'Error reading key file '\Wrox\Keys\ThePhile.snk' -- The system cannot find the path specified. '" error when I compiled. If my folder structure is: I:\wrox\ThePhile, how should I specify the path? The original code simply does not work, I have to change it to something.

Btw, my operating system and .NET framework was installed on 2 different physical hard drives.

Another question is: the book used .NET 1.0, I am having .NET 2003 installed, does it work on v1.1?

Thanks for any help.


[/quote]

Knowledge is to be shared.

I just comment-out the key signing lines in all of the AssemblyInfo lines:

//[assembly: AssemblyDelaySign(false)]
//[assembly: AssemblyKeyFile(@"c:\thephile\Keys\ThePhile.snk")]
//[assembly: AssemblyKeyName("")]

There's no reason to use strong-naming on this project - none of the assemblies are installed into the GAC. And if you do want to use a strong name for some reason, you surely don't want to use somebody else's key (ThePhile.snk).

You can convert this project for use in VS 2003 if you delete all of the .dll and .pdb files. Then you need to do a build. It will fail the first couple times. After each failure you need to refresh the references to point to the new .dll files you already built.

Eric