Visual Studio 2026 Graduates C++ Dynamic Debugging to General Availability, Letting Developers Inspect Optimized Code Without a Debug Build
Microsoft's C++ Dynamic Debugging, which deoptimizes only the targeted stack frame, left preview on November 12, 2026 for all Visual Studio 2026 channels and MSVC Build Tools 14.52.
Editor's Note ·
- Correction:
- The article quotes Michael Buschbeck as saying "Dynamic Debugging lets me work in optimized builds while still being able to deoptimize and inspect code when needed." The source (Microsoft's C++ Team Blog) actually quotes him saying: "Dynamic Debugging is a game changer for C++ development. It lets me work in the optimized builds I actually need for large game codebases, while still being able to deoptimize and inspect code and runtime state when it matters. It removes a longstanding tradeoff between realistic runtime performance and a productive debugging experience." The published sentence condenses and reworks this three-sentence statement rather than reproducing it verbatim.
- Correction:
- The article quotes Bryce Hutchings as saying "It's seamless—you forget how much it's helping." The source actually quotes him saying "It's so seamless you forget how much it's helping." The published quote omits the word "so" and alters the punctuation.
Overview
Microsoft announced that C++ Dynamic Debugging is now generally available in all Visual Studio 2026 channels and the Microsoft C++ (MSVC) Build Tools version 14.52, according to the C++ Team Blog. The feature, which the team describes as addressing “a traditional development tradeoff” between debuggable and performant builds, lets developers inspect local variables, step through source line-by-line, and step into inlined functions in a build that otherwise stays fully optimized.
What the feature does
According to the C++ Team Blog, debug builds have historically provided symbol access at the cost of performance, while optimized builds keep speed but complicate debugging because variables can show as “optimized away” and stepping can behave unreliably. C++ Dynamic Debugging is designed to combine both: functions deoptimize automatically when a developer sets a breakpoint on them or steps into them, which the blog says eliminates the need to rebuild specific sections with #pragma optimize directives. The post says the feature is intended to help developers maintain runtime performance for large games and other performance-sensitive applications while cutting the preparation time normally needed before debugging.
Two customers are quoted in the announcement. Michael Buschbeck, Principal Software Engineer at Microsoft Havok, said: “Dynamic Debugging lets me work in optimized builds while still being able to deoptimize and inspect code when needed.” Bryce Hutchings, Principal Software Engineer for Microsoft Cloud Streaming, Mixed Reality, and Graphics, said of the feature: “It’s seamless—you forget how much it’s helping.”
To turn it on in an MSBuild project, the blog says developers enable it through Configuration Properties > Advanced > Use C++ Dynamic Debugging; projects built with CMake or other systems use the /dynamicdeopt switch instead. The blog adds that Unreal Engine 5.6 and later support the feature through its own WindowsPlatform.bDynamicDebugging configuration option, and that the technology is compatible with the FastBuild and IncrediBuild distributed build systems.
From preview to general availability
Microsoft first announced the feature as a preview exclusive to the MSVC toolset in Visual Studio 2022 version 17.14 Preview 2, on March 19, 2025, according to the original C++ Team Blog post. That post described the same core mechanism — the feature “dynamically deoptimizes code that you set breakpoints on or step into” — and said that only the targeted stack frame deoptimizes while frames higher up the call stack stay optimized; a deoptimized frame is marked with a “[Deoptimized]” tag in the Call Stack window. At preview, Microsoft reported build-time costs for the feature, including an end-to-end build-time increase of 1.05x to 1.15x and an iteration-build increase of up to 1.8x for monolithic games.
The preview period drew independent attention from trade press: an InfoQ report from June 2025 covering Visual Studio 2022 v17.14 described dynamic debugging as allowing developers “to debug an optimised application build” that “will be dynamically de-optimised in the background, allowing access to the variables and code structures as they are in the source code,” noting that previously “it was required to perform a non-optimised build for debugging.”
What we don’t know
The general-availability announcement does not specify whether the build-time and binary-size overheads measured during the preview still apply at the same magnitude in the shipped version, nor does it name a specific Visual Studio 2026 update number tied to the change. Microsoft’s announcement states the feature is available “in all Visual Studio 2026 channels,” without further detail on channel-specific rollout timing.