.NET 2.0 not backwards compatible with .NET 1.1???? 2

[Ime532]

Is anyone else having problems with stuff written for .NET 1.1 not working when the client upgrades to .NET 2.0? Unless I'm missing something, how can microsoft think this is okay to release a software upgrade that breaks applications made for the previous versions????

Also, is Microsoft planning on creating .NET framework 3.0 and doing the same thing, not making it backwards compatible??? Thanks.

 

[ThatRickGuy]

So far as I know, .Net 2 is not backwards compatible with .Net 1.0 or 1.1. This is actually pretty common, software with the same version number and different release numbers are usually assumed to be backwords compatible (ie: 1.1 support 1.0). Changes in version numbers are usually such large changes that backwards support is not offered (ie: 2.0 does not support 1.1).

But you should be able to run the 1.1 and 2.0 frame work on the same PC at the same time so that any old .Net 1.1 applications can continue to run even after you install 2.0

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.

 

[Ime532]

Thank you for the reply!

Our application launches a client-side application and basically it breaks if it is the 1.1 version and the user upgraded to version 2.0. The reason this happens, as it was explained to me, is that the app tries to use the 2.0 version of any control no matter what, even if the app was written to use 1.1 versions, and that is causing it to break. Should this not be happening or can it be prevented?

 

[SHelton]

Assuming you have version 1.1 and 2.0 installed side-by-side on the same machine, apps written against 1.1 may throw exceptions. This is because if the app does not specify which version of the framework it needs, the runtime will use the most recent (i.e. 2.0), which may not implement all the methods of a previous version.

You can get round this by adding a configuration file to the 1.1 app and using the supportedRuntime element to specify which version is required:

<?xml version ="1.0"?>
<configuration>
  <startup>
    <supportedRuntime version="v1.1.4322" /> 
  </startup>
</configuration>

 

[chrissie1]

Nope this can't be the problem since 1.1 and 2.0 co-exist on the same machine in a differnt directory your problem will be somewhere else. It is perfectly possible for the client to have .net 2.0 and 1.1 on the same machine. What could have happend is that he uninstalled the 1.1 version (God knows why but users sometimes do weird things.)

Christiaan Baes
Belgium

"Time for a new sig." - Me

 

[Ime532]

Thank you for the code shelton!

Chrissie1 this is in fact the problem because every one of our clients experiences the issue. Removing .NET 2.0 framework fixes the issue for everyone as well.

 

[ThatRickGuy]

SHelton has it. I remember seeing the flag for it, but I can't remember where. It had something to do with linking in the manifest of assemblies and version numbers. It was a great article, I just can't remember where I read the damn thing.

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.