inertiave / directx-vs-templates

Direct3D Visual Studio Templates

Direct3D Game VS project templates

This repo contains simplified Visual C++ project templates. They are primarily intended for developer education, samples, and tutorials.

See this blog post and this one.

Documentation is available on GitHub.

There are two versions of each template. The DR version adds a DeviceResources (DX11 or DX12) abstraction to isolate the device and swapchain code into it's own helper class.

For the UWP templates, there are C++/WinRT variants that use C++ Windows Runtime language projections rather than the C++/CX language extensions (/ZW).

VS 2017

The VSIX\Direct3DUWPGame.vsix supports Visual Studio 2017. Use of the Visual Studio 2017 15.9 update is recommended.

The package requires the Universal Windows Platform development workload (Microsoft.VisualStudio.Workload.Universal) with the C++ Universal Windows Platform tools (Microsoft.VisualStudio.ComponentGroup.UWP.VC). The Win32 templates require the Desktop development with C++ workload (Microsoft.VisualStudio.Workload.NativeDesktop). It is recommended you make use of the Windows 10 October 2018 Update SDK (17763) or alter.

VS 2019

The VSIX\Direct3DUWPGame.vsix also works for VS 2019.

The package requires the Universal Windows Platform development workload (Microsoft.VisualStudio.Workload.Universal) with the C++ Universal Windows Platform tools (Microsoft.VisualStudio.ComponentGroup.UWP.VC). The Win32 templates require the Desktop development with C++ workload (Microsoft.VisualStudio.Workload.NativeDesktop). It is recommended you make use of the Windows 10 October 2018 Update SDK (17763) or later.

Rebuilding the VSIX

Building the VSIX project requires VS 2017 with the Visual Studio extension development (Microsoft.VisualStudio.Workload.VisualStudioExtension) and .NET desktop development (Microsoft.VisualStudio.Workload.ManagedDesktop) workloads.

Notices

All content and source code for this package are subject to the terms of the MIT License.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.