-->
  1. Platform Toolset 141 Download
  2. Platform Toolset V110
  3. Platform Toolset Download
  4. Visual Studio Install Platform Toolset

Apps built by using Visual Studio can be targeted to various platforms, as follows.

To get the Visual Studio 2017 platform toolset and components to target Windows XP and Windows Server 2003, run the Visual Studio Installer. When you initially install Visual Studio or when you modify an existing installation, make sure the Desktop development with C workload is selected. In the list of optional components for this workload, choose Windows XP support for C, and then choose. Platform Toolset V141 Windows 10 Version 1903; Platform Toolset V141 Install Either V141; The following are the configurations of my VS2019 and I can build the solution successfully. Platform Toolset V141 Install Either V141. If you have VS 2019, you dont need the v141 tools, because it should install either v141 or v142 by default anyway. The Visual C build tools workload in the Visual Studio Build Tools will install the latest v141 toolset from VS2017 by default. The v140 toolset from VS2015 will install side-by-side with the v141 toolset. To install them just select the “VC 2015.3 v140 toolset for desktop (x86,x64)” at the bottom of the “Optional” section.

Operating Systemx86x64ARMARM64****
Windows XPX*X*
Windows Server 2003X*X*
Windows VistaXX
Windows Server 2008XX
Windows 7XX
Windows Server 2012 R2XX
Windows 8XXX
Windows 8.1XXX
Windows 10XXXX
Android **XXXX
iOS **XXXX
Linux ***XXXX

* You can use the Windows XP platform toolset included in Visual Studio 2017, Visual Studio 2015, Visual Studio 2013, and Visual Studio 2012 Update 1 to build Windows XP and Windows Server 2003 projects. For information on how to use this platform toolset, see Configuring Programs for Windows XP. For additional information on changing the platform toolset, see How to: Modify the Target Framework and Platform Toolset.

** You can install the Mobile development with C++ workload in the installer for Visual Studio 2017 and later. In Visual Studio 2015 setup, choose the optional Visual C++ for Cross Platform Mobile Development component to target iOS or Android platforms. For instructions, see Install Visual C++ for Cross-Platform Mobile Development. To build iOS code, you must have a Mac computer and meet other requirements. For a list of prerequisites and installation instructions, see Install And Configure Tools to Build using iOS. You can build x86 or ARM code to match the target hardware. Use x86 configurations to build for the iOS simulator, Microsoft Visual Studio Emulator for Android, and some Android devices. Use ARM configurations to build for iOS devices and most Android devices.

*** You can install the Linux development with C++ workload in the installer for Visual Studio 2017 and later to target Linux platforms. For instructions, see Download, Install and Setup the Linux Workload. This toolset compiles your executable on the target machine, so you can build for any supported architecture.

**** ARM64 support is available in Visual Studio 2017 and later.

For information about how to set the target platform configuration, see How to: Configure Visual C++ Projects to Target 64-Bit, x64 Platforms.

Platform Toolset 141 Download

See also

-->

The Windows Driver Kit (WDK) takes advantage of the MSBuild platform toolset feature to provide tools and libraries that are specific to driver development. The MSBuild platform toolset feature is extensible. The specific version of the platform toolset that you want to use is controlled by an MSBuild property called PlatformToolset. Projects can switch between tools and libraries by setting the PlatformToolset property in the project file.

The Windows Driver Kit (WDK) 8.1 provides the following platform toolsets for driver development.

Platform Toolset 141 Download

PlatformToolset (WDK 8.1)Use
WindowsKernelModeDriver8.1For kernel-mode drivers and components.
WindowsUserModeDriver8.1For user-mode drivers and components.
WindowsApplicationForDrivers8.1For any type of application. This platform toolset provides compatibility with the build options used in the Windows Driver Kit (WDK) for Windows 7 (WDK 7.1), and also uses the default settings that are common for development of user-mode applications that interact with drivers. You might use this setting if you are migrating or converting a project that was built using WDK 7.
Visual Studio 2013 (v120)Use for any type of Windows application (default).

The Windows Driver Kit (WDK) 8 provided the following platform toolsets for driver development. This information is provided for reference only.

PlatformToolset (WDK 8)Use
WindowsKernelModeDriver8.0For kernel-mode drivers and components.
WindowsUserModeDriver8.0For user-mode drivers and components.
WindowsApplicationForDrivers8.0For any type of application. This platform toolset provides compatibility with the build options used in the WDK for Windows 7 (WDK 7.1). You might use this setting if you are migrating or converting a project that was built using WDK 7.
Visual Studio 2012 (v110)Use for any type of Windows application (default).

Note If you create a driver from one of the available Windows driver templates in Visual Studio, the PlatformToolset property is set for you. You can also select the PlatformToolset by using the driver project property page in Visual Studio.Setting the Platform Toolset in Visual Studio

  1. Open the property pages for your driver project. Select and hold (or right-click) the driver project in Solution Explorer and select Properties.
  2. In the property pages for the driver project, select Configuration Properties and then select General.
  3. Select the Platform Toolset property for the project from the drop-down list.

Example - Setting the PlatformToolset property in a Visual Studio project file (.vcxproj)

The following example shows how the PlatformToolset property is set in the project file.

The ConfigurationType property controls the target extension and the output type for the binary that is being built. Some of the possible values for this property are Application, DynamicLibrary, StaticLibrary, and Utility.

The WDK introduces a new value for this property called Driver to build a kernel-mode driver. If you set this property to Driver, MSBuild will generate a driver file with .sys as its extension. In the example, the PlatformToolset property is set to WindowsKernelModeDriver8.1 to build a kernel-mode driver. WindowsKernelModeDriver8.1 is the only WDK platform toolset that requires the DriverConfigurationType. In this example, the DriverType is set to KMDF.

About the PlatformToolset property for drivers

The PlatformToolset is a set of property sheets, targets, tools, and tasks that work together to extend and modify a platform in order to build drivers or kernel-mode components for that particular platform. For drivers and related components and applications, the PlatformToolset property should be set to WindowsKernelModeDriver8.1, WindowsUserModeDriver8.1, or WindowsApplicationForDrivers8.1 in the project file. These platform toolsets are designed to extend the existing Visual Studio CC++ tool chain compiler and linker with other WDK-specific build tools and target the WDK headers and libraries. The WindowsApplicationForDrivers8.1 toolset provides compatibility with the build option settings that were available in the WDK for Windows 7 (WDK 7.1), and also the default settings that are common for development of user-mode applications that interact with drivers.

The Platform Toolset has the default platform-level settings and targets to build any driver project. You use default switches for build tools such as the compiler or linker, system information such as the INCLUDE or LIBRARY paths for the WDK, and feature settings such as various properties to set when using Unicode or ANSI strings to build a driver project. If you are developing a Windows application for the desktop, do not use the WindowsKernelModeDriver8.1, WindowsUserModeDriver8.1, or WindowsApplicationForDrivers8.1 platform toolset. Instead, use the Visual Studio 2013 (v120) platform toolset.

By default, the PlatformToolset property is Visual Studio 2013 (v120) for both newly created Win32 user mode C++ projects and projects that were converted to Visual Studio 2013. In both cases, the PlatformToolset property is not written to the project file.

When you select one of the platform toolsets for drivers, the following properties are set.

  • ExecutablePath and NativeExecutablePath (PATH)
  • IncludePath (INCLUDE)
  • ReferencePath (LIBPATH)
  • LibraryPath (LIB)
  • SourcePath
  • ExcludedPath

Note When UseEnv is not set to TRUE, PATH, LIB, INCLUDE, LIBPATH will be set from the corresponding property values in the platform toolset. When UseEnv is set to TRUE, as in the old build system, the values from the environment variables for PATH, INCLUDE, LIB, and LIBPATH will be used instead.

Platform Toolset V110

Where the WDK installs files that enable the driver-specific platform toolsets

Platform Toolset Download

The following table summarizes the places where the WDK installs files to enable the platform toolsets for driver development.

Visual Studio Install Platform Toolset

Path variableDescription

$(VCTargetsPath)

By default, $(VCTargetsPath) is defined in the registry as $(MSBuildExtensionsPath)<em><FOLDER><MSBUILDSYNTAXVERSION>)

The version number is included in case a new build process is used for the same platform, which has new syntax and requires a later MSBuild.

The <FOLDER> is the Microsoft.Cpp folder - $(MSBuildExtensionsPath)Microsoft.Cpp4.0v120.

This is called syntax version rather than tools version. It is the assembly version of the first Microsoft.Build.Engine that supports all of the necessary syntax. Microsoft.Cpp indicates the only folder where Visual Studio will look for platforms.

$(VCTargetsPath)Platforms$(Platform)ImportAfter.props

Optional folder that does not normally contain files. You can customize the platform by saving MSBuild format files in this folder. They will be imported at the bottom of the platform settings file, as indicated by the folder that they are currently in. The order in which files are imported from this location is undefined. The files that MSBuild creates are $(VCTargetsPath)Platforms$(Platform)ImportAfterMicrosoft.Cpp.<Platform>.WindowsKernelModeDriver8.1.props and Microsoft.Cpp.<Platform>.WindowsUserModeDriver8.1.props, which import several WDK-specific props files.

$(VCTargetsPath)Platforms$(Platform)PlatformToolsets$(PlatformToolset)</p>

Brute force attack app download for android real and working. For the WDK:

The $(PlatformToolset) must be set to WindowsKernelModeDriver8.1 for building kernel mode drivers, set to WindowsUserModeDriver8.1 for building user mode drivers, and set to WindowsApplicationForDrivers8.1 for compatibility with the build options used in the Windows 7 WDK (WDK 7).

PlatformToolset Directory

For example, C:Program FilesMSBuildMicrosoft.Cppv4.0v120PlatformsWin32PlatformToolsetsWindowsKernelModeDriver8.1.

The PlatformToolsets directory allows you to add other types of files later – in their own subfolder.

Pokemon sun and moon download for mac. Microsoft.Cpp.$(Platform).$(PlatformToolset).props

Platform Toolset Props file

Imports props files to build a driver. Also imports v120 props file.

Microsoft.Cpp.$(Platform).$(PlatformToolset).targets

Platform Toolset Targets file

Imports target files to build a driver. These files contain <UsingTask> tags to pull in the WDK tasks. This feature also imports v120 targets.

$(WDKContentRoot)build.props

All driver specific props files. These files contain default settings to build a driver.

$(WDKContentRoot)build*.targets

All driver specific targets file. This file identifies the targets to build a driver.