Quote:
Originally Posted by pilotbob
Actually, the versioning on .Net is pretty good, if not a bit confusing. .Net 1.0 and .Net 1.1 included new runtimes... Where .Net 2.0, 3.0, 3.5 all use the same 2.0 CLR/Runtime but each of 3.0 and 3.5 added new libraries, tools and compilers. So, yes if you want to install .Net 3.5 it has to include .Net 2.0/3.0.
Of course they are going to confuse it all with .Net 4.0 which is going to include a new CLR/Runtime again AFAIK.
Although, I don't see an issue with having several versions of .Net on a PC as a problem.
|
It's like the Good Old Days of Visual Basic runtimes. New versions were not supersets of older ones. You had to install the specific ones your applications wanted.
And I've seen a case where a mission critical app that wanted .NET 1.1 failed if .NET 2.0 was also installed in the machine, which made life interesting because another mission critical app required 2.0...
Quote:
|
But, the myth that if a .Net app runs on one machine it will run on any one is certainly not true and really farking with me today.
|
There are exceptions to any rule, and you get to deal with them. The Director of Developement at a former employer was eloquent about Java not necessarily being "write once, run anywhere", as he'd seen too much non-portable Java code...
______
Dennis