Strong name validation failed

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Sehboo - 24 Oct 2007 20:41 GMT

One more try since I don't have the option to remove PublicKeyToken as
somebody pointed that here..

We are using enterprise library (EL) in our application. We want to
upgrade our application from .net 1.1 to .net 2.0. Since we have
changed code in enterprise library, we can't just go with the newer
version, we will have to keep the old version.

All out assemblies are strongly named!

I recompiled all the projects in EL with VS 2005, but if I try to run
EntLibConfig.exe then I get the error that Could not load file or
assembly EntLibConfig.exe or one of its dependency. Strong name
validation failed.

All the projects were compiled with the same old public key.

Here are the entries in our GlobalAssemblyInfo.cs file

[assembly: AssemblyDelaySign(true)]
[assembly: AssemblyKeyFile(@"c:\shared\keys\prod-Public.snk")]
[assembly: AssemblyKeyName("")]

Anybody knows what I need to do?

thanks

Reply to this Message

Andrew Faust - 25 Oct 2007 04:45 GMT

I don't think it's possible to do what you want. I believe when you sign an
assembly it uses the key, version, name & a hash of the actual file. This
way you have a guarantee that the file hasn't been tampered with. If it
didn't do a check against the hash of the file there would be nothing to
prevent someone from modifying an assembly in a hex editor and adding their
own code.

You're going to need to keep the old and new versions of your library.
Keeping it around shouldn't be a problem, though. Since your assemblies are
strongly typed the 1.1 and 2.0 versions can coeexist in the GAC jsut fine.

Signature

Andrew Faust
andrew[at]andrewfaust.com
http://www.andrewfaust.com

> One more try since I don't have the option to remove PublicKeyToken as
> somebody pointed that here..
[quoted text clipped - 22 lines]
>
> thanks

Reply to this Message

Rate this thread:

Strong name validation failed

Free Magazines