Strong-Name 1.1 module incompatible with 2.0

G

Guest

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
 
C

Christopher Reed

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

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

.Net 2.0 compatability with 1.1 5
Upgrading from .NET Framwork 1.1 to 2.0 4
Microsoft .NET Framework 2.0 Configuration (Management Console inwindows control panel) only with SD 2
Dot NET 2.0a not installed 9
Performance hit running 1.1 assembly in 2.0? 2
possibly a simple question 4
.NET Framework 1.1 installation after 2.0 2
VISTA and installing .NET 1.1 15

Top