"Strong name validation failed for assembly xxx"

29 Mar 2006 4:37 AM

Randolph Neall

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

29 Mar 2006 4:00 PM

Randolph Neall

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.

Show quote

"Randolph Neall" <randolphne***@veracitycomputing.com> wrote in message
news:OhO2tluUGHA.4436@TK2MSFTNGP10.phx.gbl...
> 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
>
>