-subsystemversion (Visual Basic)
Specifies the minimum version of the subsystem on which the generated executable file can run, thereby determining the versions of Windows on which the executable file can run. Most commonly, this option ensures that the executable file can leverage particular security features that aren’t available with older versions of Windows.
To specify the subsystem itself, use the -target compiler option.
The minimum required version of the subsystem, as expressed in a dot notation for major and minor versions. For example, you can specify that an application can't run on an operating system that's older than Windows 7 if you set the value of this option to 6.01, as the table later in this topic describes. You must specify the values for
minor as integers.
Leading zeroes in the
minor version don't change the version, but trailing zeroes do. For example, 6.1 and 6.01 refer to the same version, but 6.10 refers to a different version. We recommend expressing the minor version as two digits to avoid confusion.
The following table lists common subsystem versions of Windows.
|Windows version||Subsystem version|
|Windows Server 2003||5.02|
|Windows Server 2008||6.01|
The default value of the -subsystemversion compiler option depends on the conditions in the following list:
The default value is 6.02 if any compiler option in the following list is set:
The default value is 6.00 if you're using MSBuild, you're targeting .NET Framework 4.5, and you haven't set any of the compiler options that were specified earlier in this list.
The default value is 4.00 if none of the previous conditions is true.
Setting this option
To set the -subsystemversion compiler option in Visual Studio, you must open the .vbproj file and specify a value for the
SubsystemVersion property in the MSBuild XML. You can't set this option in the Visual Studio IDE. For more information, see "Default values" earlier in this topic or Common MSBuild Project Properties.