Help with framework hell

[Frank Rizzo]

I have a customer with my winform app that was written .net 1.1. It has
worked fine till now. He has just installed .net framework 2.0 and all
of a sudden the application is having all kinds of problems.

I thought that if the application is written in vs2003, it will by
default use .net 1.1 framework. Is this not the case?

What else should I be looking at?

Thanks.

 

[Lyny]

Hi,
I am not sure how but there is a way to specify what version of the
framework the program must use.
Look into that direction.

 

[Guest]

Frank,
Sounds to me like they may have uninstalled .NET 1.1. That's the first place
I'd look.
--Peter

 

[Frank Rizzo]

Frank,
Sounds to me like they may have uninstalled .NET 1.1. That's the first place
I'd look.
--Peter

That is the first place I looked at, but it was not meant to be an easy
problem to deal with.

I did the standard filemon/regmon/fuslogvw thing and the winapp does go
against 1.1 assemblies. However, it also goes against mscoree.dll,
which is the .NET execution engine. There is only one copy of
mscoree.dll (in windows/system32) and the 2.0 overwrote the 1.1 version.
So it's not really side by side on this DLL. Could this be an issue?

 

[Brendan Green]

To force an application to use a specific version of the framework, add this
to the app.config:

<configuration>
<startup>
<requiredRuntime version="v1.0.3705" safemode="true"/>
</startup>
</configuration>

Obviously, change the version to whatever you're targeting.

 

[Greg Young]

This has changed in 2.0 from the way it worked in 1.x ... see
http://blogs.msdn.com/junfeng/archive/2004/04/16/114108.aspx

Cheers,

Greg Young
MVP - C#