Skip to main content
This article describes Microsoft Game Development Kit (GDK) support for Visual Studio 2019. Visual Studio 2019 version 16.11 supports GDK development.
Visual Studio 2019 versions 16.0 through 16.10 are out of support as of October 2022. Version 16.11 is also out of main-stream support.

Installing Visual Studio 2019

The GDK supports development with either the Professional edition or the Enterprise edition of Visual Studio 2019. The Community edition isn’t supported. When installing Visual Studio 2019, select the Game development with C++ workload during setup as shown in the following screenshot. In addition to the core C++ tools that you need for game development, make sure the Windows 10 SDK (22000) component is installed to provide the Windows SDK required to build games with the GDK. The Windows SDK for Windows 11, Version 22H2 (10.0.22621), or Windows SDK for Windows 11, Version 24H2 (10.0.26100) can also be used, but isn’t required. While it’s not required, installing the Desktop development with C++ workload provides more tools and samples that you might find helpful. Version v142 of the MSVC build tools is installed with the Game development with C++ workload.
The Visual Studio 2017 v141 toolset is no longer supported as of the October 2024 release.

clang/LLVM for Windows (ClangCl) project support

Visual Studio 2019 also supports clang/LLVM for Windows development. This support requires installing C++ Clang-cl for Windows and C++ Clang-cl for v142 build tools (x64/x86), which are individual components. For more information, see the Microsoft Game Development Kit (GDK) Clang article and the Microsoft Docs.

Build Tools edition

Use Build Tools for Visual Studio 2019 to build with the Microsoft GDK headers, libraries, and tools by following the Build With/Out Install instructions.
  • Use the workload Desktop Development with C++ which installs the Visual C++ compiler for PlatformToolset v142. You can also select components for ClangCl support per the instructions earlier in this article.
  • Install the Windows SDK or use it as a NuGet package.
The Build Tools edition doesn’t support extensions, so you can’t install the Microsoft GDK’s VSIX packages for the Build Edition. This limitation means it doesn’t support deployment or debugging, although you can use command-line tools.

Migrating existing Visual Studio 2017 projects to Visual Studio 2019

In most cases, the upgrade wizard provided with Visual Studio can migrate your project to Visual Studio 2019 without any other changes. When you open a Visual Studio 2017 project in Visual Studio 2019, you see the following Review Solution Actions dialog box that prompts you to upgrade. To upgrade the project, select OK. You can also choose to use the Visual Studio 2019 IDE without upgrading your build tools. To do so, select Cancel in the Review Solution Actions dialog box.

Manually upgrading projects to Visual Studio 2019

If you want to upgrade your project by directly editing your project files (.vcxproj), make the following changes.
  1. Change all instances of PlatformToolset from v141 to v142. The following example shows how to make this change.
  1. Rebuild the project.

Using specific versions

By default, the Visual Studio Installer always downloads the latest release. In an Enterprise setting, you can control the specific version by using an offline layout. For more information, see Controlling updates to Visual Studio deployments. That article also provides information about removing the VS notification icon. Download specific versions of Visual Studio 2019 from Visual Studio 2019 Releases.

Known issues

  • DirectXMath *IsNan functions can fail with Visual Studio 2019 when built with /fp:fast. The fix is to use Visual Studio 2019 (16.3 or later). Otherwise, you can work around the issue by placing #pragma float_control statements around the use of those functions.
  • Only the 64-bit native compiler toolset is supported for GDK development. In a Visual C++ vcxproj, set this toolset in the globals properties:

Reporting bugs

Report bugs for the Visual C++ compiler (if possible) through Visual Studio Report a Problem…. See Microsoft Docs and the Developer Community website. For details on creating a good bug report for the compiler, see this page.
You can add a comment to a public report issue marked as “Microsoft only” if other NDA information is required to reproduce the issue.
For bug reporting for the clang/LLVM for Windows compiler, use https://bugs.llvm.org/ For bug reports for the Microsoft Standard C++ Library (also known as STL), use https://github.com/microsoft/STL/issues As always, feel free to reach out to your Microsoft Representative for critical issues that need escalation.

See also

Visual Studio Visual Studio Product Lifecycle and Servicing
Last modified on August 14, 2026