Of course it is always better to not write any bugs, but I know I make mistakes. So sooner or later I need to debug my code to find what’s going wrong.
In that case breakpoints are an important aid to halt your application at the right location. Visual Studio 2022 introduces 2 new breakpoint types; temporary and dependent breakpoints:
The Temporary breakpoint is used to set a breakpoint that will only break once. When debugging, the Visual Studio debugger only pauses the running application once for this breakpoint and then removes it immediately after it has been hit.
To set a temporary breakpoint, hover over the breakpoint symbol, choose the Settings icon, and then select Remove breakpoint once hit in the Breakpoint Settings window:
You can also use the right-click context menu to set the temporary breakpoint by selecting Insert Temporary Breakpoint from the context menu:
The Dependent breakpoint is used to set a breakpoint that will only break when another breakpoint is hit. This can make debugging code in common paths such as game loop or a utility API much easier because a breakpoint in those functions can be configured to enable only if the function is invoked from a specific part of your application.
To set a dependent breakpoint, hover over the breakpoint symbol, choose the Settings icon, and then select Only enable when the following breakpoint is hit in the Breakpoint Settings window.
In the dropdown, select the prerequisite breakpoint you want your current breakpoint to be dependent on.
You can also use the right-click context menu to set the dependent breakpoint by selecting Insert Dependent Breakpoint from the context menu:
