Re: VB.NET 2008 not backward compatable?
- From: "Herfried K. Wagner [MVP]" <hirf-spam-me-here@xxxxxx>
- Date: Fri, 17 Apr 2009 19:29:57 +0200
"Mike Williams" <Mike@xxxxxxxxxxxxxxxxx> schrieb:
I also believed that if a computer had any .NET framework, my
code would run on it as it would be backward compatable. Boy
am I naive. I sent someone an .exe who has .NET framework
1.1 and it wouldn't launch, saying "v2.0.5072" was required.
You would be better off ditching Micro$oft altogether. They love doing this kind of stuff to people. Just ditch them and ditch Vb.Net and go somewhere else for your programming tools.
Sorry, but that's nonsense. It's pretty clear that applications compiled against a *newer* version of a library won't work with older versions. Almost any .NET 2.0 application makes use of features which are not present in older versions of the .NET Framework. (Sure, there are differences in the CLR which prevent execution of .NET 2.0+-based assemblies on the .NET 1.* CLR.)
VB6-based applications didn't run on the VB5 runtime libraries too. But there is one significant difference: .NET 1.1-based applications will run on newer versions of the CLR, whereas an application developed using VB5 won't run on a system which provides the VB6 runtime files only.
--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>
.
- Follow-Ups:
- Re: VB.NET 2008 not backward compatable?
- From: Michel Posseth [MCP]
- Re: VB.NET 2008 not backward compatable?
- References:
- VB.NET 2008 not backward compatable?
- From: tiki99 via DotNetMonster.com
- Re: VB.NET 2008 not backward compatable?
- From: Mike Williams
- VB.NET 2008 not backward compatable?
- Prev by Date: Problem reading css file
- Next by Date: Re: Problem reading css file
- Previous by thread: Re: VB.NET 2008 not backward compatable?
- Next by thread: Re: VB.NET 2008 not backward compatable?
- Index(es):
Relevant Pages
|