Geek Answers Handbook

Why .net 4.6.1 is needed when 4.5.2 is in the target structure

I have one friend with Windows 7 (x64). For this OS, .net 4.6.1 is not supported. I have Windows 10 (x64) on my computer with vs community 2015 installation, and everything works fine here.

So, when my friend tries to run my application, he receives a request to install .net 4.6.1.

In the project "Target structure" in the project. NET Framework 4.5.2

Crutches from Microsoft?

and what can i do to fix this?

+5
source share
1 answer

From here :

The .NET Framework 4.6 is an in-place update for all of the following versions of the .NET Framework:

  • .NET Framework 4
  • .NET Framework 4.5
  • .NET Framework 4.5.1
  • .NET Framework 4.5.2

An in-place upgrade means that if you install the .NET Framework 4.6 when any of the above versions of the .NET Framework is installed on your computer, installing the .NET Framework 4.6 will update them and you will only be left with the .NET Framework 4.6 installed. In addition, any attempt to install older versions of the .NET Framework 4 family when the .NET Framework 4.6 is already present will result in the installation of the .NET Framework blocking you from installing because it detects that a newer version is already installed.

The .NET Framework 4.6 is designed to be compatible with all applications built with any version of the .NET Framework from 4 to 4.6, but sometimes there are application compatibility issues, such as the installer, which tells the user that they should install the .NET Framework 4.5, even if the .NET Framework 4.6 is already installed. In such cases, you may need to revert from the .NET Framework 4.6 to an earlier version of the .NET Framework 4 family. To do this, you must uninstall the .NET Framework 4.6 and then reinstall the earlier version of the .NET Framework from the .NET Framework 4 family.

Basically, you are invited to install 4.6.1, because it is the highest version compatible with your program oriented to 4.5.2, and the target machine does not seem to have a compatible framework (4.5.2 or higher).

+16
source

More articles:


All Articles