Installing .NET Framework

[Guest]

I recently re-installed Windows XP using a generic Windows XP disc on a Dell computer. Everything is fine except now I want to install the .NET Framework and I'm not sure what to do. Do I simply download install .NET Framework 3.5 SP1? Or do I have to install each component so .NET Framework 2.0, 3.0, 3.5, 3.5 SP1?

 

Also, should I install .NET Framework 4.0 and what benefits do I get from installing 4.0? If I install 4.0 do I not need to install the previous instances?

 

Thanks.

[CTskifreak]

Just do it through Microsoft/Windows update. I've just kept it updated because of improved benefits and security.

 

AJ

[Aethec]

.NET programs will only work on a given version of the .NET Framework.

If you don't use software written in a .NET language, there's no need to install the .NET Framework.

 

Installing 3.5 SP1 (~250 MB) will install .NET 2 and 3 and too, however installing .NET 4.0 will not due to technical reasons. .NET 4 comes in two profiles : Client and Extended. Most software only need the Client part (~40 MB)

[Guest]

Thanks guys. I completely forgot Windows Update.

[Andavari]

I wish Microsoft had the newest versions completely backwards compatible so all those previous versions wouldn't be needed. I've got multiple software titles that require most of the versions be installed. I haven't installed anything yet that requires 4.0, although I have the 4.0 Client installed from Microsoft Update.

[Aethec]

I wish Microsoft had the newest versions completely backwards compatible so all those previous versions wouldn't be needed. I've got multiple software titles that require most of the versions be installed. I haven't installed anything yet that requires 4.0, although I have the 4.0 Client installed from Microsoft Update.

 

This is impossible, sadly.

There are two major things in .NET: Libraries and the Common Language Runtime, or CLR.

The CLR is responsible for transforming CIL code (the code in which all .NET language are compiled) into native code.

Libraries contain methods to do things, and are compiled for a specific CLR version.

 

.NET 3.0, 3.5 and 3.5 SP1 only added libraries - huge updates (WPF made its appearance in .NET 3.0) but they were compiled for version 2 of the CLR, and thus the CLR itself remained unchanged. Which is why installing .NET 3.5 SP1 installs .NET 2, 3 and 3.5 too.

.NET 4 has not only new libraries, but also a new CLR version, which means all software compiled for previous .NET versions will not work on it (the opposite is true, too; a .NET 2 program cannot run on .NET 4). Thus, it does not install previous .NET versions since they are not needed.

A nice touch in .NET 4 is that the "Client Profile" is exactly that - a client profile, containing all basic libraries. If you need more, you just have to install the Extended Profile. In .NET 3.5 SP1, the Client Profile was a huge mess - you couldn't install anything on top of it to get the full .NET framework, which made it useless.