VS Mac .NET Core tutorials #18819
VS Mac .NET Core tutorials #18819
Conversation
tdykstra
requested review from
BillWagner and
CamSoper
and removed request for
a team
|
|
||
| The program displays the string that the user enters. What happens if the user doesn't enter anything? You can test this with a useful debugging feature called a *conditional breakpoint*. | ||
|
|
||
| 1. Right-click (<kbd>Ctrl</kbd>+click on macOS) on the red dot that represents the breakpoint. In the context menu, select **Edit Breakpoint** to open a dialog that lets you enter a conditional expression. |
There was a problem hiding this comment.
Just curious, what is the reason not to use <kbd> here? I ask because I use it everywhere and now I'm wondering if I shouldn't.
There was a problem hiding this comment.
Ctrl-click seems to be a special case mixing keyboard and mouse, so I decided to leave it the way it was in the Mac tutorials as they already existed. I'm happy to change if you've seen Mac tutorials using <kbd>Ctrl</kbd>-click
There was a problem hiding this comment.
ping @BillWagner on how best to render control-click for macOS in tutorials
There was a problem hiding this comment.
Hmmm. I don't have a clear recommendation. I think the <kbd>Ctrl</kbd>-click is best.
There was a problem hiding this comment.
A related issue: given that Macs have keyboard labels all in lowercase (enter, control, option, command, etc., should those keys be represented by, e.g., <kbd>command</kbd> or <kbd>Command</kbd>
There was a problem hiding this comment.
As with the earlier question, I don't have an answer here. I think we will set the standard.
My weakly held proposal: go with lower case to match the keyboard labels.
BillWagner
left a comment
BillWagner
left a comment
There was a problem hiding this comment.
This also LGTM. You can 
when ready.
| 1. Select the **Terminal** tab, and press any key to exit the program and stop debugging. | ||
|
|
||
| 1. Clear the breakpoint by clicking on the dot in the left margin of the code window. Another way to clear a breakpoint is by pressing <kbd>F9</kbd> while the line of code is selected. | ||
| 1. Clear the breakpoint by clicking on the dot in the left margin of the code window. Another way to clear a breakpoint is by choosing **Run > Toggle Breakpoint** while the line of code is selected. |
There was a problem hiding this comment.
Other steps have a "or press KEY" alternative, this one was removed, I think it should be added back 😄
There was a problem hiding this comment.
The intent was to make it more mac-friendly by not mentioning function keys, and it seemed to me not a loss because you see the keyboard shortcut on the menu when you do the menu selection. But I'll add the F9 text for the set and clear breakpoint steps.
|
|
||
| A *breakpoint* temporarily interrupts the execution of the application before the line with the breakpoint is executed. | ||
|
|
||
| 1. Set a breakpoint on the line that displays the name, date, and time. To do that, place the cursor in the line of code and press ⌘ \\ (<kbd>Command</kbd>+<kbd>\\</kbd>). Another way to set a breakpoint is by selecting **Run** > **Toggle Breakpoint** from the menu. |
There was a problem hiding this comment.
What about using <kbd>⌘</kbd> for the symbols? Looks like this: ⌘+↵
5 participants
Fixes #18512
Fixes #18513
Fixes #18749
In addition to creating the VS Mac series, this PR makes the 3 "swim lanes" as similar as possible, so some changes were made to the VS and VS Code series as well.