Strong-Name 1.1 module incompatible with 2.0

24 Jan 2006 11:18 PM

Steven J. Reed

I have modules that have been strong-named with .Net Framework 1.1. When
these modules are installed on a machine which has .Net Framework 2.0, I
receive an error code 8013150D -- COR-E-VERIFICATION error.

If .Net Framework 2.0 is removed form the machine, the modules work fine.

I'm not ready to recompile these modules with .Net Framework 2.0. Any
suggestions on how to get around this problem?

Thanks...Steve

25 Jan 2006 10:14 AM

Christopher Reed

You need to make some configuration changes to make this work. Look at the
supportedRuntime element in the MSDN documentation.

--
Christopher A. Reed
"The oxen are slow, but the earth is patient."

Show quote

"Steven J. Reed" <StevenJR***@discussions.microsoft.com> wrote in message
news:D6EA7064-7A3D-4FF7-BAC3-9D47779A3B83@microsoft.com...
>I have modules that have been strong-named with .Net Framework 1.1. When
> these modules are installed on a machine which has .Net Framework 2.0, I
> receive an error code 8013150D -- COR-E-VERIFICATION error.
>
> If .Net Framework 2.0 is removed form the machine, the modules work fine.
>
> I'm not ready to recompile these modules with .Net Framework 2.0. Any
> suggestions on how to get around this problem?
>
> Thanks...Steve