We recommend using Visual Studio 2017

AllowLaterVersions Property (Launch Conditions)

Specifies whether a version of the .NET Framework runtime that is later than the version specified in the Version property can be installed on the target computer.

NoteNote:

The AllowLaterVersions property was available in the integrated development environment (IDE) in Visual Studio 2005. Although it is still available, it is no longer available in the IDE. You can still modify the property in the project file. For information about how to do this, see Using MSBuild to Target Specific .NET Framework Versions.

The settings for the AllowLaterVersions property are as follows:

Setting

Description

True

A later version of the .NET Framework runtime can be installed.

False

A later version of the .NET Framework runtime cannot be installed (default).

When an application to be installed requires the .NET Framework, a custom action (CheckFX) in Windows Installer determines what version of the .NET Framework is installed on the target computer. The custom action then sets a launch condition based on the result. Before the application is installed, the launch condition property Version in the Setup project specifies the exact version of the .NET Framework that the installer requires.

AllowLaterVersions specifies whether a later version of the .NET Framework runtime can be installed on the target computer. This property was provided so that applications created for the .NET Framework 1.0 or 1.1 platforms would not be installed on computers on which later versions are installed.

For example, suppose that you specify a version of 1.1.4322 for your application's .NET Framework launch condition. Prior to installation, .NET Framework 2.0 was present on the target computer, but .NET Framework 1.1 was not. The installation will fail unless you install .NET Framework 1.1 and then install your application again. This is because .NET Framework 2.0 does not satisfy the launch condition requiring version 1.1. This is an issue only with versions 1.0 and 1.1. It is not an issue when equal or later versions are installed over versions 2.0, 3.0, and 3.5, because 3.5 includes 3.0, and 3.0 includes 2.0.

The default setting of AllowLaterVersions is False, specifying that the .NET Framework version on the target computer must match the Version value that you specify in the launch condition.

Community Additions

Show: