Forcing a .NET framework 1.1 application to use .NET framework 2.0 without creating application conf

5 Apr 2007 6:02 AM

pdabak

Hello,

I have a console application that is compiled using VS 2003 and hence
targetted for .NET 1.1 runtime. This application uses some shared
assemblies (my own) that were also initially compiled using VS 2003
and hence targetted for .NET 1.1.

Recently we have moved those shared assemblies to .NET 2.0. However
the console application is not yet moved to .NET 2.0. Now, when this
console application runs, it fails to load those shared assemblies
since the application uses .NET framework 1.1 runtime and the shared
assemblies it requires are now .NET 2.0. If I create a application
config file for the console application to use .NET 2.0, it all works
fine.

However, creating an application config file is not a feasible option
for us since there are many such applications and some of them are
packaged in our installers and we don't want to rebuild those
installers with the application config files.

The question is: Is there any way to force a set of applications to
always use .NET 2.0 without explicitly creating application config
files?

Any help will be much appreaciated.

Thanks.
-Prasad

5 Apr 2007 8:21 AM

Clive Dixon

There is a registry key you can set - see the section "Test 4" at:

http://msdn2.microsoft.com/en-us/library/ms994387.aspx

<pda***@yahoo.com> wrote in message
Show quote

news:1175752953.990942.73470@o5g2000hsb.googlegroups.com...
> Hello,
>
> I have a console application that is compiled using VS 2003 and hence
> targetted for .NET 1.1 runtime. This application uses some shared
> assemblies (my own) that were also initially compiled using VS 2003
> and hence targetted for .NET 1.1.
>
> Recently we have moved those shared assemblies to .NET 2.0. However
> the console application is not yet moved to .NET 2.0. Now, when this
> console application runs, it fails to load those shared assemblies
> since the application uses .NET framework 1.1 runtime and the shared
> assemblies it requires are now .NET 2.0. If I create a application
> config file for the console application to use .NET 2.0, it all works
> fine.
>
> However, creating an application config file is not a feasible option
> for us since there are many such applications and some of them are
> packaged in our installers and we don't want to rebuild those
> installers with the application config files.
>
> The question is: Is there any way to force a set of applications to
> always use .NET 2.0 without explicitly creating application config
> files?
>
> Any help will be much appreaciated.
>
> Thanks.
> -Prasad
>

5 Apr 2007 10:37 AM

Clive Dixon

Should have also noted that if you have a machine with 1.1 & 2.0 installed,
config files won't help you anyway - a 1.1 app will still use 1.1 (except
for add-ins running under native apps). See Table 1 at

http://msdn2.microsoft.com/en-us/library/ms994381.aspx