F9 #6550
F9 #6550
Conversation
|  | ||
|
|
||
| 5. Add a breakpoint to your project by clicking on the **editor margin**, which is the space on the left of the line numbers in the editor, next to line 9. | ||
| 5. Add a breakpoint to your project by clicking on the **editor margin**, which is the space on the left of the line numbers in the editor, next to line 9, or put mouse cursor on line 9 and press <kbd>F9</kbd>. |
There was a problem hiding this comment.
Where the breakpoint is placed when you press F9 is not controlled by the mouse cursor, but by the text cursor. So I think it's confusing to talk about the mouse cursor here and you should change it to talk about the text cursor instead.
rpetrusha
added
the
✨ 1st-time docs contributor!
There was a problem hiding this comment.
Thank you for contributing to the dotnet/docs repo, @dzmitry-lahoda, and for adding an alternate way to set a breakpoint. Ordinarily, our introductory tutorials try to show just one way to perform a UI interface action. Since customers sometimes have difficulty setting a breakpoint by clicking in the editor margin, an exception is warranted in this case. I would, however, like to you make two additional corrections before we merge your PR.
|  | ||
|
|
||
| 5. Add a breakpoint to your project by clicking on the **editor margin**, which is the space on the left of the line numbers in the editor, next to line 9. | ||
| 5. Add a breakpoint to your project by clicking on the **editor margin**, which is the space on the left of the line numbers in the editor, next to line 9, or move text cursor into line 9 in the editor and then press <kbd>F9</kbd>. |
There was a problem hiding this comment.
move text cursor into --> move the text cursor onto
and then press --> and press
There was a problem hiding this comment.
Thank you, @dzmitry-lahoda, for making the additional changes. We'll merge your PR now. Your changes should appear live on docs.microsoft.com in the next day or two.
5 participants
teach new devs for good
debug break via f9