Skip to content

Commit a41628b

Browse files
committed
Art update
1 parent 41d2939 commit a41628b

File tree

2 files changed

+9
-1
lines changed

2 files changed

+9
-1
lines changed

docs/debugger/get-started-with-breakpoints.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ To set a breakpoint in source code:
4545

4646
- Click in the far left margin next to a line of code. You can also select the line and press **F9**, select **Debug** > **Toggle Breakpoint**, or right-click and select **Breakpoint** > **Insert breakpoint**. The breakpoint appears as a red dot in the left margin.
4747

48-
For most languages, including C#, Visual Studio automatically highlights breakpoint and current execution lines. For C++ code, you can turn on highlighting of breakpoint and current lines by selecting **Tools** (or **Debug**) > **Options** > **Debugging** > **Highlight entire source line for breakpoints and current statement (C++ only)**.
48+
For most languages (including C#), Visual Studio automatically highlights breakpoint and current execution lines. For some languages, such as C++, which isn't highlighted by default, you can turn on highlighting of breakpoint and current lines by selecting **Tools** (or **Debug**) > **Options** > **Debugging** > **Highlight entire source line for breakpoints and current statement (C++ only)**.
4949

5050
::: moniker range=">= vs-2022"
5151
![Set a breakpoint](../debugger/media/vs-2022/basic-breakpoint.png "Basic breakpoint")
@@ -54,6 +54,8 @@ For most languages, including C#, Visual Studio automatically highlights breakpo
5454
![Set a breakpoint](../debugger/media/basicbreakpoint.png "Basic breakpoint")
5555
::: moniker-end
5656

57+
To debug, press **F5** or select **Debug** > **Start Debugging**.
58+
5759
When you debug, execution pauses at the breakpoint, before the code on that line is executed. The breakpoint symbol shows a yellow arrow.
5860

5961
::: moniker range=">= vs-2022"
@@ -70,6 +72,12 @@ At the breakpoint in the following example, the value of `testInt` is still 1. S
7072

7173
When the debugger stops at the breakpoint, you can look at the current state of the app, including [variable values](../debugger/debugger-feature-tour.md#inspect-variables-with-data-tips) and the [call stack](../debugger/how-to-use-the-call-stack-window.md).
7274

75+
::: moniker range=">= vs-2022"
76+
For example, in the following illustration, you can see the value of `testInt` in a datatip and in the **Locals** window.
77+
78+
![Screenshot of viewing app state](../debugger/media/vs-2022/basic-breakpoint-viewing-app-state.png)
79+
::: moniker-end
80+
7381
Here are a few general instructions for working with breakpoints.
7482

7583
- The breakpoint is a toggle. You can click it, press **F9**, or use **Debug** > **Toggle Breakpoint** to delete or reinsert it.
26.9 KB
Loading

0 commit comments

Comments
 (0)