"Strong name validation failed for assembly xxx"

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Randolph Neall - 29 Mar 2006 05:37 GMT

After converting to VS 2005 an assembly that used to run in a certain
directory just fine does not do so any longer. Loading it results in the
error "strong name validation failed for assembly xxx." It happens that this
assembly is not strongly named, and it runs without error in other
directories on the same computer. But it does not run where it used to run.

This assembly runs as a service on Windows Server 2003.

Running SN.exe for this situation does not work and is useless.

What's up? What to do?

Randy Neall

Reply to this Message

Randolph Neall - 29 Mar 2006 16:56 GMT

The problem has been solved, but I'm not quite sure why. We simply recopied
the .dll's into the directory; perhaps one had been bad or missing.

> After converting to VS 2005 an assembly that used to run in a certain
> directory just fine does not do so any longer. Loading it results in the
[quoted text clipped - 9 lines]
>
> Randy Neall

Reply to this Message

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...