tags:

views:

698

answers:

2

Lets say I have an old application which will try to load an external assembly.

  • The old application is compiled to CLR 2.
  • The new assembly is compiled to CLR 4.

I would like to be able to run that old application inside CLR 4. I remember there was some xml manifest magic involved.

How can I create that manifest xml file to tell that oldapplication.exe shall run under CLR 4?

I found some suggestions, but they do not seem to work for me.

oldapplication.exe.config:

<?xml version ="1.0"?>
<configuration>
 <startup>
      <!--set the appropriate .net version-->
      <requiredRuntime version="4.0.0.0"/>
 </startup>
</configuration>


While giving another shot i found this file to serve as my template:

C:\Windows\Microsoft.NET\Framework\v4.0.20506\Aspnet_regsql.exe.config

<?xml version ="1.0"?>
<configuration>
    <startup>
        <supportedRuntime version="v4.0.20506"/>
        <requiredRuntime version="v4.0.20506" safemode="true"/>
    </startup>
</configuration>

I also updated the code to report current CLR:

Console.WriteLine(typeof(object).Assembly.ImageRuntimeVersion);

It works now!

A: 

I believe you want to use supportedRuntime, not requiredRuntime.

"The <supportedRuntime> element should be used by all applications built using version 1.1 or later of the runtime." (http://msdn.microsoft.com/en-us/library/a5dzwzc9.aspx). Mke sure the version string exactly matches "the installation folder name" for the version you want.

Matthew Flaschen
+4  A: 

You need to give the proper version number. Note that this is the beta 1 version, it will change until RTM settles one:

<configuration>
 <startup>
      <supportRuntime version="4.0.20506"/>
 </startup>
</configuration>
Jb Evain