BUILD / Stage 02
Build environment
Reproduce the supported legacy toolchain and dependency layout before changing an example.
Identify the supported legacy Windows toolchain before cloning dependencies.
Requirements
The official examples target a legacy Windows-native toolchain. Prepare Visual Studio 2019 or newer as the IDE, the Visual C++ 2010 x64 toolset, the June 2010 DirectX SDK, and Git with Git LFS.
Build the examples as Release / x64. The upstream examples explicitly warn that their Debug configuration is broken; this guide does not present Debug as a supported alternative.
Obtain the LFS-backed dependency repository and run its setup process.
Clone dependencies
Clone the official examples and the companion dependency repository with Git. The dependency repository uses Git LFS, so downloading its ZIP does not provide a reliable equivalent.
After cloning the dependencies, run its Setup.bat as directed upstream. Keep the repository layout expected by the example solution so project references resolve without hand-rewriting paths.
Select the expected compiler, architecture, SDK, and build configuration.
Configure the toolchain
Open the official example solution in Visual Studio and select the expected architecture and configuration:
- Platform: x64
- Configuration: Release
- Compiler/toolset: Visual C++ 2010 x64 (v100)
- SDK: DirectX · June 2010
Treat these constraints as project requirements, not modern-toolchain recommendations. Establish a known-good build before attempting an upgrade or migration experiment.
Check the cloned examples and dependencies before changing project code.
Verify the workspace
Before editing example code, verify that Git LFS objects are present, dependency setup completed, the solution can see its include and library paths, and Visual Studio exposes the requested Release/x64 configuration.
If the official setup cannot be reproduced, compare your filesystem layout and toolchain selection with upstream first. The community working solution linked on this site is a supplementary reference, not project authority.