Solved Question regarding .NET updates (Can I install 4.6.2 and skip 4-4.5)?

[b89]

I have been searching online about requirements for installing .NET Framework (subsequent versions and updates).

Question: Can I just install .NET 4.6.2 and avoid subsequent versions (4, 4.5, 4.5.1, etc) or do I need to lets say install .NET 4.5 first? The current version of .NET framework I have installed is 4.6.2, which came through Windows update.

Second question - when a program says Requires .NET 4.0 or 4.5 in it's system requirements - can't it be handled by .NET 4.6 or does it require installation of the older version?


System State/Updates Installed:
I did a Windows 7 Clean install (64-bit w/ SP1)
-Manually updated WUA to the latest version to avoid the hour long scans).
-Installed IE11 prior to running Windows Update
-Ran the Update cycle. All "Important" ones have been installed except KB 3205402
(Dec 2016 .NET update all versions)


Apparently .NET 3.5 is installed with Windows 7.


Thanks to anyone who can provide information - I couldn't find much guidance in KB articles or the.NET blog?


-I did skip the "Platform Update"

 

[Pyprohly]

Question: Can I just install .NET 4.6.2 and avoid subsequent versions (4, 4.5, 4.5.1, etc) or do I need to lets say install .NET 4.5 first? The current version of .NET framework I have installed is 4.6.2, which came through Windows update.

Imagine the criticism they’d get if they had users run around the ‘net trying to locate every .NET Framework installer that preceded their required version, and then have them spend time installing each one of them before they could use their application. Installing previous versions is usually never the case with any software.

If a known breaking change is to be introduced between, say versions 4 and 4.6, the 4.6 installer would install any intermediate frameworks that weren’t compatible. But generally, versions with the same major version number don’t try to introduce anything breaking. Everything is always done at the ease of the user.

See here for more details.

All of the .NET Framework versions listed in the following table are in-place updates to the .NET Framework 4. In other words, if you install a later version, such as the .NET Framework 4.6, you do not first have to install the previous versions, such as the .NET Framework 4.5, 4.5.1, or 4.5.2. Similarly, if you install a later version, such as the .NET Framework 4.6, you do not first have to uninstall the previous versions, such as the .NET Framework 4.5, 4.5.1, or 4.5.2. This also means that you cannot install an earlier version listed in the table if a later version is already installed.

Second question - when a program says Requires .NET 4.0 or 4.5 in it's system requirements - can't it be handled by .NET 4.6 or does it require installation of the older version?

.NET 4.6 will handle it.

Apparently .NET 3.5 is installed with Windows 7.

Most, if not, all machines since Windows 7 have .NET 3.5 installed. I believe the underlying CLR technology got an upgrade since this version.

 

[b89]

Imagine the criticism they’d get if they had users run around the ‘net trying to locate every .NET Framework installer that preceded their required version, and then have them spend time installing each one of them before they could use their application. Installing previous versions is usually never the case with any software.

If a known breaking change is to be introduced between, say versions 4 and 4.6, the 4.6 installer would install any intermediate frameworks that weren’t compatible. But generally, versions with the same major version number don’t try to introduce anything breaking. Everything is always done at the ease of the user.

See here for more details.



.NET 4.6 will handle it.


Most, if not, all machines since Windows 7 have .NET 3.5 installed. I believe the underlying CLR technology got an upgrade since this version.

Thank you!

That is awesome. I read some conflicting things and wasn't sure particularly with AV programs w/ .NET installers on the disc. I installed 4.6.2, no issues. The CLR service (.NET Optimization) runs faster now (Yay!).

I was ignorant. I really appreciate your time - and now I won't forget that.

Have an awesome week.