[BUG] Improve C# Dev Kit Debugging Walkthrough

[bamurtaugh]

Describe the Issue

Following the steps in the doc, I'm unclear if I should use the Run and Debug view or not when I'm using the C# Dev Kit.

I was thinking yes as it's mentioned in docs and in the getting started walkthrough:

But based on the results and some other info in docs, I'm not sure.

Steps To Reproduce

1. Open Run and Debug view, see I don't have any launch configurations
2. Follow steps in doc to select a C# launch config
3. Try using Run and Debug
4. I don't see the output of my console app

Expected Behavior

I expected to see my console app's "Hello, World!" output in the terminal the same way I see the output when I use F5.

Environment Information

I'm using a .NET dev container with the latest VS Code Insiders on Windows 11 Insiders.

Version: 1.80.0-insider (user setup)
Commit: 79c4092768e41b16fd823e80c874dbfafdc08f55
Date: 2023-06-13T05:21:23.732Z
Electron: 22.5.5
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.25387

[WardenGnaw]

Do you see the output in the Debug Console tab?

By default, the settings for output is set to the internalConsole. You can change this option in your User Settings.
See https://code.visualstudio.com/docs/csharp/debugging#_user-settings

[bamurtaugh]

Ah yes, I see it if I go to the Debug Console, thank you!

I think it'd be helpful to highlight that in the walkthrough and/or an FAQ section of the debug doc. Right now the walkthrough points me to docs and to open the Run and Debug, and just opening Run and Debug isn't sufficient to see my output.

[WardenGnaw]

Ideally VS Code should focus on Debug Console if the console type is set to internalConsole or focus on Terminal if set to integratedTerminal or with externalWindow a popup for the output should show. But I can improve the docs on the walk through .

[bamurtaugh]

Ideally VS Code should focus on Debug Console if the console type is set to internalConsole or focus on Terminal if set to integratedTerminal or with externalWindow a popup for the output should show.

@Tyriar @connor4312 would this be a feature request for VS Code core? (tagging you both for the terminal and debugging aspect)

[WardenGnaw]

Added notes, console is our launch.json configuration option, but VS Code should get a runInTerminal request if we set it to integratedTerminal. If not it should default to showing the Debug Console.

[connor4312]

VS Code should focus on Debug Console if the console type is set to internalConsole or focus on Terminal if set to integratedTerminal or with externalWindow a popup for the output should show.

This is already the case, and is configurable by users.

[bamurtaugh]

This is already the case, and is configurable by users.

The original issue I filed is because VS Code stayed focused on the integrated terminal, though the output was set to Debug Console, so I didn't see anything when I first ran. I could manually change my focus to the Debug Console to see the output, which I didn't expect since I thought other extensions automatically changed my focus. But perhaps this is expected?

[Tyriar]

@bamurtaugh it's controlled bydebug.internalConsoleOptions, I have it set to "neverOpen" so I'm just assuming it still works.

[bamurtaugh]

Thanks @Tyriar. Looks like mine is openOnFirstSessionStart, so maybe what happened is:

• I ran once and debug console opened
• I tried running again, and debug console didn't open because it wasn't my first session

[WardenGnaw]

In a newer version of C# Extension, you should be able to input ReadLine/Read with the Debug Console.

See dotnet/vscode-csharp#6569