Note: parameters below work only in case the target app is launched into the debugger and will not work if you are attaching the debugger to an already running process.
Can be enabled by the console field with the internalConsole value in the Launch Request.
VSCode IDE: Add the "console": "internalConsole" property to your .vscode/launch.json configuration file.
VSCode will then include the console field with the internalConsole value in the Launch Request.
When using internalConsole, you can input text that will be returned from Console.ReadLine and similar APIs that read from stdin by sending an Evaluate Request with the text you need. Note that if you send an Evaluate Request with text while your program is stopped under the debugger, this text will be evaluated as a C# expression, not sent to the target process.
To do so in VSCode, while the program is running, type text into the input box at the bottom of the Debug Console in VSCode IDE. Pressing Enter will send the text to the target process.
More info: https://aka.ms/VSCode-CS-LaunchJson-Console
Can be enabled by the console field with the remoteConsole value in the Launch Request.
Note: VSCode IDE doesn't support the remoteConsole value for the console property in the .vscode/launch.json configuration file.
When using remoteConsole, the debugger will start a local server and open a TCP port for connection. Users can use an external program (for example, netcat - nc localhost 22534) as an external terminal. When using this mode, you will need to switch focus between the IDE and the external program. All input from the external program will be routed to the target process stdin, and all target process stdout and stderr streams will be routed to the external program as well.
The default TCP port used is 22534. This can be changed by providing the remoteConsolePort field with a port number value in the Launch Request.