<h3>BACKGROUND</h3> As I understand it, in a C++ project: <ul> <li>Project Properties => Configuration Properties => General => Platform Toolset <ul> <li>Tells the compiler which SDK to physically compile against.</li> <li>For example: v140 will tell Visual Studio 2015 to use the latest and greatest v8.1 Windows SDK</li> </ul> </li> <li> <code>_WIN32_WINNT</code>, <code>WINVER</code>, and <code>NTDDI_VERSION</code> macros <ul> <li>Depending on the underlying operating system, an SDK function can have a different function signature from OS-to-OS.</li> <li>SDKs are suppose to be backward compatible. 1 </li> <li>The before mentioned macros enable you to specify which version of a function you wish to compile against.</li> </ul> </li> </ul> <h3>MY QUESTION</h3> If I compile my application with the following setup: <ul> <li>project properties => configuration properties => General => Platform Toolset <ul> <li>set to: <code>v140_xp</code> (Visual Studio 2015 - Windows XP)</li> <li>Setting tells compiler to use the 7.1 SDK, which makes sense.</li> </ul> </li> <li>content of: <code>StdAfh.h</code> <ul> <li><code>#include <WinSDKVer.h></code></li> <li><code>#define _WIN32_WINNT 0x0501</code></li> <li><code>#define WINVER 0x0501</code></li> <li><code>#define NTDDI_VERSION 0x05010000</code></li> <li><code>#include <SDKDDKVer.h></code></li> <li>Macros tell compiler which function signatures to use, which makes sense.</li> </ul> </li> </ul> From what I can tell, it looks like Target Platform Version is an suposed to be an alternative to the <code>_WIN32_WINNT</code>, <code>WINVER</code>, and <code>NTDDI_VERSION</code> macros. The weird thing is, with the above configuration you can set the Target Platform Version to <code>1</code> or <code>99</code>... and the compiler doesn't generate any errors or warnings. This this leaves me wondering: What is the Target Platform Version for? <h3>ADDITIONAL CONTEXT</h3> <ul> <li>Compiler: Visual Studio 2015</li> </ul> <h3>REFERENCES</h3> <ul> <li>Windows SDK Brokenness</li> <li>Target Platform Version general project property on VS2015</li> <li>Using the Windows Headers</li> <li>What is WINVER?</li> <li>Modifying WINVER and _WIN32_WINNT</li> <li>Visual Studio setting WINVER/_WIN32_WINNT to Windows 8 on Windows 7?</li> </ul> <h3>EDIT HISTORY</h3> <ul> <li>2016/09/21: As per Hans' comment, macros have been updated to reference Windows XP.</li> </ul>

In Visual Studio 2015 the Target Platform Version field just sets the version of the Windows SDK to use. See this MSDN article for reference. In Visual Studio 2019, this field has been renamed Windows SDK Version. You still need to set <code>_WIN32_WINNT</code>, <code>WINVER</code>, and <code>NTDDI_VERSION</code> macros, as well as the Platform Toolset field. Taken together they determine the versions of Windows your app can run on. If your applications need to run on Windows XP, you have to pick a Platform Toolset ending in _xp, select an older Windows SDK Version (you need 7.1A, but picking 7.0 or 8.1 should work; see below), and set <code>_WIN32_WINNT</code>, <code>WINVER</code>, and <code>NTDDI_VERSION</code> macros accordingly. See this Stack Overflow posting for tips on setting these macros and including related SDK headers via <code>targetver.h</code>. If building from a Command Prompt with an _xp platform toolset see this Stack Overflow posting for tips on setting the <code>/SUBSYSTEM</code> linker option and for defining <code>_USING_V110_SDK71_</code>. Windows SDKs are backward-compatible, but I haven't yet found a clear reference which lists the oldest version of Windows you can target when building with a given version of the Windows SDK (see EDIT at the bottom of this post). Each SDK lists "System Requirements", but these list the minimum version of Windows needed to develop with the SDK, not the minimum version of Windows that executables built with that SDK can target. The best reference I know of is the <code>sdkddkver.h</code> header in each of the newer Windows SDKs. Within this header are a list of _WIN32_WINNT version constants. For example, in the Windows 7.1A SDK, <code>sdkddkver.h</code> defines <code>_WIN32_WINNT_NT4</code> as the oldest supported Windows platform (but I do not know if this is definitive). The rest of this answer are notes regarding targeting for native VC++ apps using Visual Studio 2019. These notes may apply to older Visual Studio versions as well. <hr> In Visual Studio 2019, selecting a Platform Toolset which ends in _xp has certain quirks. For v120_xp, the Windows SDK Version field is hidden, but the inherited VC++ Directories will show that the Windows SDK 7.1A directory is specified. For v140_xp and v141_xp platform toolsets, you can pick Windows SDK 7.0 or 8.1 (for either, the inherited VC++ Directories will show that the Windows SDK 7.1A directory is specified). I am not sure what the difference is - if any - between specifying Windows SDK Version 7.0 or 8.1 when using Platform Toolset v140_xp or v141_xp in Visual Studio 2019. In Visual Studio 2019, when setting native C++ project properties for a Windows Desktop app, depending on the Platform Toolset you select, the read-only Target Platform field may change to "Windows 10". But this DOES NOT mean your Win32 desktop app will be built as a Universal Windows Platform app. It will still work on older versions of Windows depending on the Platform Toolset, Windows SDK Version and the values for the <code>_WIN32_WINNT</code>, <code>WINVER</code>, and <code>NTDDI_VERSION</code> macros. Microsoft could update VS2019 so the Target Platform field value would show just "Windows" when setting properties for Win32/desktop projects, regardless of the selected Platform Toolset or Windows SDK Version. EDIT: See the article A Brief History of Windows SDKs from Chuck Walbourn, Senior Engineer for Xbox at Microsoft, for details regarding backward compatibility of various Windows SDKs.

The following summarizes the differences between the Windows SDK Version & the Platform Toolset configuration properties. <h3>Windows SDK Version</h3> Important: Sometimes this property is referred to as <code>Target Platform Version</code> Thankfully, this subject has been updated in Microsoft's MSDN. The following was taken directly from C++ project property pages. <blockquote> this specifies the version of the Windows SDK that your project requires. When you install a C++ Workload by using the Visual Studio installer, the required parts of the Windows SDK are also installed. If you have other Windows SDK versions on your computer, each version of the SDK tools that you have installed appears in the dropdown. To target Windows 7 or Windows Vista, use the value 8.1, since Windows SDK 8.1 is backward compatible to those platforms. In addition, you should define the appropriate value for _WIN32_WINNT in targetver.h. For Windows 7, that's 0x0601. </blockquote> For those of you who don't know, any given Windows SDK is [mostly] backwards compatible with older versions of the Windows SDK. For example, you could configure your C++ project with the following: <ol> <li>C++ project => Properties => Configuration Properties => General <ul> <li>Target Platform Version = <code>10</code> <ul> <li>This SDK enables you to leverage the capabilities of the Windows 10 operating system.</li> </ul> </li> </ul> </li> <li>Add a header file called <code>TargetVer.h</code> to your project that includes the following pre-processor macros: <ul> <li><code>#define WINVER 0x0603 // Windows 8.1</code></li> <li><code>#define _WIN32_WINNT 0x0603 // Windows 8.1</code></li> </ul> </li> </ol> For more information, please see: <ul> <li>What is SDKDDKVer.h for?</li> <li> Modifying WINVER and _WIN32_WINNT <ul> <li>Includes a list of constants for the various SDKs.</li> </ul> </li> <li>See summary of: Windows SDK options </li> </ul> <h3>Platform Toolset</h3> This property specifies the following for your C++ project: <ol> <li>the compiler <ul> <li>For example: <code>v142</code> results in the the Visual Studio 2019 compiler being used</li> </ul> </li> <li>the Visual C++ library <ul> <li>For example: <code>v142</code> indicates that you are using the Visual Studio 2019 C++ library <ul> <li>Which means that, your application will need the Visual Studio 2019 C++ Redistributable (<code>MSVCRxxx.dll</code>) during deployment.</li> </ul> </li> <li> <code>MSVCR</code> <ul> <li> <code>MS</code> = Microsoft</li> <li> <code>V</code> = Visual</li> <li> <code>C</code> = C++</li> <li> <code>R</code> = Redistributable</li> </ul> </li> <li>The redistributable is installed to: <ul> <li><code>C:\Windows\</code></li> <li><code>C:\Windows\SysWOW64\</code></li> </ul> </li> <li>Your application can determine which C++ library is being used by referencing the <code>_MSC_VER</code> pre-processor macro.</li> </ul> </li> </ol> It is worth noting that: <ol> <li>The <code>Platform Toolset</code> is a project level setting (see <code>PlatformToolset</code> in <code>*.vcxproj</code>), whereas, the selected <code>Windows SDK Version</code> is saved elsewhere.</li> <li>The name of a <code>Platform Toolset</code> value can be somewhat confusing because: <ul> <li>The value (e.g. <code>v142</code>) is associated with a Visual Studio release (e.g. Visual Studio 2019)</li> <li>Rather than install the Visual Studio IDE, you can install Build Tools. This is useful when working with build machines.</li> </ul> </li> </ol> For more information, please see: <ul> <li>See summary of: Platform Toolset options </li> <li>C++ Binary Compatibility and Pain-Free Upgrades to Visual Studio 2019</li> <li> Predefined PreProcessor Macros <ul> <li>Includes a list of possible <code>_MSC_VER</code> values and their meanings</li> </ul> </li> <li>Announcing Visual C++ Build Tools 2015</li> </ul>

What does the `Target Platform Version` mean for a VS C++ project?

BACKGROUND

As I understand it, in a C++ project:

Project Properties => Configuration Properties => General => Platform Toolset
- Tells the compiler which SDK to physically compile against.
- For example: v140 will tell Visual Studio 2015 to use the latest and greatest v8.1 Windows SDK
_WIN32_WINNT, WINVER, and NTDDI_VERSION macros
- Depending on the underlying operating system, an SDK function can have a different function signature from OS-to-OS.
- SDKs are suppose to be backward compatible. 1
- The before mentioned macros enable you to specify which version of a function you wish to compile against.

MY QUESTION

If I compile my application with the following setup:

project properties => configuration properties => General => Platform Toolset
- set to: v140_xp (Visual Studio 2015 - Windows XP)
- Setting tells compiler to use the 7.1 SDK, which makes sense.
content of: StdAfh.h
- #include <WinSDKVer.h>
- #define _WIN32_WINNT 0x0501
- #define WINVER 0x0501
- #define NTDDI_VERSION 0x05010000
- #include <SDKDDKVer.h>
- Macros tell compiler which function signatures to use, which makes sense.

From what I can tell, it looks like Target Platform Version is an suposed to be an alternative to the _WIN32_WINNT, WINVER, and NTDDI_VERSION macros. The weird thing is, with the above configuration you can set the Target Platform Version to 1 or 99... and the compiler doesn't generate any errors or warnings.

This this leaves me wondering: What is the Target Platform Version for?

ADDITIONAL CONTEXT

Compiler: Visual Studio 2015

REFERENCES

Windows SDK Brokenness
Target Platform Version general project property on VS2015
Using the Windows Headers
What is WINVER?
Modifying WINVER and _WIN32_WINNT
Visual Studio setting WINVER/_WIN32_WINNT to Windows 8 on Windows 7?

EDIT HISTORY

2016/09/21: As per Hans' comment, macros have been updated to reference Windows XP.

420

asked Sep 21 '16 16:09

Pressacco

2 Answers

In Visual Studio 2015 the Target Platform Version field just sets the version of the Windows SDK to use. See this MSDN article for reference. In Visual Studio 2019, this field has been renamed Windows SDK Version. You still need to set _WIN32_WINNT, WINVER, and NTDDI_VERSION macros, as well as the Platform Toolset field. Taken together they determine the versions of Windows your app can run on.

If your applications need to run on Windows XP, you have to pick a Platform Toolset ending in _xp, select an older Windows SDK Version (you need 7.1A, but picking 7.0 or 8.1 should work; see below), and set _WIN32_WINNT, WINVER, and NTDDI_VERSION macros accordingly. See this Stack Overflow posting for tips on setting these macros and including related SDK headers via targetver.h.

If building from a Command Prompt with an _xp platform toolset see this Stack Overflow posting for tips on setting the /SUBSYSTEM linker option and for defining _USING_V110_SDK71_.

Windows SDKs are backward-compatible, but I haven't yet found a clear reference which lists the oldest version of Windows you can target when building with a given version of the Windows SDK (see EDIT at the bottom of this post). Each SDK lists "System Requirements", but these list the minimum version of Windows needed to develop with the SDK, not the minimum version of Windows that executables built with that SDK can target. The best reference I know of is the sdkddkver.h header in each of the newer Windows SDKs. Within this header are a list of _WIN32_WINNT version constants. For example, in the Windows 7.1A SDK, sdkddkver.h defines _WIN32_WINNT_NT4 as the oldest supported Windows platform (but I do not know if this is definitive).

The rest of this answer are notes regarding targeting for native VC++ apps using Visual Studio 2019. These notes may apply to older Visual Studio versions as well.

In Visual Studio 2019, selecting a Platform Toolset which ends in _xp has certain quirks. For v120_xp, the Windows SDK Version field is hidden, but the inherited VC++ Directories will show that the Windows SDK 7.1A directory is specified. For v140_xp and v141_xp platform toolsets, you can pick Windows SDK 7.0 or 8.1 (for either, the inherited VC++ Directories will show that the Windows SDK 7.1A directory is specified).

I am not sure what the difference is - if any - between specifying Windows SDK Version 7.0 or 8.1 when using Platform Toolset v140_xp or v141_xp in Visual Studio 2019.

In Visual Studio 2019, when setting native C++ project properties for a Windows Desktop app, depending on the Platform Toolset you select, the read-only Target Platform field may change to "Windows 10". But this DOES NOT mean your Win32 desktop app will be built as a Universal Windows Platform app. It will still work on older versions of Windows depending on the Platform Toolset, Windows SDK Version and the values for the _WIN32_WINNT, WINVER, and NTDDI_VERSION macros.

Microsoft could update VS2019 so the Target Platform field value would show just "Windows" when setting properties for Win32/desktop projects, regardless of the selected Platform Toolset or Windows SDK Version.

EDIT: See the article A Brief History of Windows SDKs from Chuck Walbourn, Senior Engineer for Xbox at Microsoft, for details regarding backward compatibility of various Windows SDKs.

183

answered Oct 11 '22 22:10

MikeOnline

The following summarizes the differences between the Windows SDK Version & the Platform Toolset configuration properties.

Windows SDK Version

Important: Sometimes this property is referred to as Target Platform Version

Thankfully, this subject has been updated in Microsoft's MSDN. The following was taken directly from C++ project property pages.

this specifies the version of the Windows SDK that your project requires. When you install a C++ Workload by using the Visual Studio installer, the required parts of the Windows SDK are also installed. If you have other Windows SDK versions on your computer, each version of the SDK tools that you have installed appears in the dropdown.

To target Windows 7 or Windows Vista, use the value 8.1, since Windows SDK 8.1 is backward compatible to those platforms. In addition, you should define the appropriate value for _WIN32_WINNT in targetver.h. For Windows 7, that's 0x0601.

For those of you who don't know, any given Windows SDK is [mostly] backwards compatible with older versions of the Windows SDK. For example, you could configure your C++ project with the following:

C++ project => Properties => Configuration Properties => General
- Target Platform Version = 10
  - This SDK enables you to leverage the capabilities of the Windows 10 operating system.
Add a header file called TargetVer.h to your project that includes the following pre-processor macros:
- #define WINVER 0x0603 // Windows 8.1
- #define _WIN32_WINNT 0x0603 // Windows 8.1

For more information, please see:

What is SDKDDKVer.h for?
Modifying WINVER and _WIN32_WINNT
- Includes a list of constants for the various SDKs.
See summary of: Windows SDK options

Platform Toolset

This property specifies the following for your C++ project:

the compiler
- For example: v142 results in the the Visual Studio 2019 compiler being used
the Visual C++ library
- For example: v142 indicates that you are using the Visual Studio 2019 C++ library
  - Which means that, your application will need the Visual Studio 2019 C++ Redistributable (MSVCRxxx.dll) during deployment.
- MSVCR
  - MS = Microsoft
  - V = Visual
  - C = C++
  - R = Redistributable
- The redistributable is installed to:
  - C:\Windows\
  - C:\Windows\SysWOW64\
- Your application can determine which C++ library is being used by referencing the _MSC_VER pre-processor macro.

It is worth noting that:

The Platform Toolset is a project level setting (see PlatformToolset in *.vcxproj), whereas, the selected Windows SDK Version is saved elsewhere.
The name of a Platform Toolset value can be somewhat confusing because:
- The value (e.g. v142) is associated with a Visual Studio release (e.g. Visual Studio 2019)
- Rather than install the Visual Studio IDE, you can install Build Tools. This is useful when working with build machines.

For more information, please see:

See summary of: Platform Toolset options
C++ Binary Compatibility and Pain-Free Upgrades to Visual Studio 2019
Predefined PreProcessor Macros
- Includes a list of possible _MSC_VER values and their meanings
Announcing Visual C++ Build Tools 2015

answered Oct 11 '22 21:10

Pressacco

Related questions
                            
                                Application Verifier fails to start on 3 separate Windows machines here
                            
                                Why is the empty base class optimization (EBO) is not working in MSVC?
                            
                                How to generate .sln/.vcproj using qmake
                            
                                C++ No main() function?
                            
                                How to display a non-modal CDialog?
                            
                                How do I create both a .lib file and an .exe file in Visual C++?
                            
                                What is stored in this 26KB executable?
                            
                                Visual C++ Precompiled Headers errors
                            
                                catch(...) is not catching an exception, my program is still crashing
                            
                                Break point in release mode
                            
                                Visual C++ Redistributables without using VCRedist_x86.exe
                            
                                C++11 std::thread vs windows CreateThread [closed]
                            
                                What is the best way to attach a debugger to a process in VC++ at just the right point in time?
                            
                                Measuring exception handling overhead in C++
                            
                                multi-word addition using the carry flag
                            
                                Azure DevOps pipeline build locally with YAML
                            
                                Using libs/dlls compiled in Linux/MinGW in Visual Studio
                            
                                %(AdditionalIncludeDirectories) meaning
                            
                                LNK1201 Visual C++ 2010 Large project failing to generate PDB
                            
                                Why can't I specify the calling convention for a constructor(C++)?

Donate For Us

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!

Donate Us With

What does the `Target Platform Version` mean for a VS C++ project?

Tags:

sdk

visual-c++

visual-studio-2015

BACKGROUND

MY QUESTION

ADDITIONAL CONTEXT

REFERENCES

EDIT HISTORY

Pressacco

People also ask

2 Answers

MikeOnline

Windows SDK Version

Platform Toolset

Pressacco

Recent Activity

Donate For Us