Re: Cryptographic failure while signgin assembly

Chris.S — Mon, 22 Jun 2009 19:27:27 GMT

It seems there is a bug in VS 2008, because I worked around the problem as follows. I invoked "sn" from the SDK command line, and created "snk" files that way (rather than using the GUI and creating a "pfx" file). I was then able to use that keypair snk file in the Signing tab of the Web Deployment Project without any error.

Cryptographic failure while signgin assembly

Chris.S — Mon, 22 Jun 2009 17:53:30 GMT

Using the Properties > Signing tab of my main project, I created a pfx file.

Then I did "Add Web Deployment Project" and in it's Properties window, I turned on "Enable strong naming", and gave it the key file (pfx) that I had just generated. Attemping to build the deployment project results in Cryptographic faliure while signing assembly. C:\Windows\Microsoft.NET\Framework\v2.050727\Temporary ASP.NET Files\my.csproj\341......\App_global.asax.dll -- 'Bad version of provider.'

Umm. What now?

Maybe I was supposed to do something else?

VS Web Deployment Projects

Re: Cryptographic failure while signgin assembly

Cryptographic failure while signgin assembly