Visual Studio 2022 Debug Console does not honour font size.

[dirkrheeder]

Windows Terminal version

1.16.10262.0

Windows build number

22621.1702

Other Software

Visual Studio 2022 17.6.2

Steps to reproduce

1. Set Windows Terminal as the default terminal application
2. Change Profile -> Visual Studio Debug Console -> Appearance -> Font Size to 30
3. Start a new Console Application with Visual Studio 2022, with the standard Console.WriteLine("Hello, World!"); and press F5 (Debug)
4. Notice that the Debug Console that opens up, does not honour the font change.
5. Change Change Profile -> Visual Studio Debug Console -> Appearance -> Font Size to 10
6. Rerun Console Application created in step 3.
7. Notice, the Debug Console that opens up, does not honour the font change.

Expected Behavior

I expect the font size in the console window that opens up to change, according to that which is set in the settings.

Actual Behavior

The font size is ignored.

[javierdlg]

@dirkrheeder Is the debug console using a new Windows Terminal window or is it using the integrated terminal within Visual Studio?

[dirkrheeder]

@javierdlg It is using an external Windows Terminal Window. I don't think you can output to an internal window in Visual Studio 2022, unlike VS Code. When you press F5 (Debug) it launches a new Windows Terminal Window, which incidentally is the right size (as in my custom defined size) just not the right font size.

I have very bad eyesight, so everything on my system uses large fonts, which is why I noticed this.

[lhecker]

I believe I understand why this happens... This Visual Studio Debug Console profile specifies a command line of just "vsdebugconsole.exe", but the application is spawned with an absolute path in the command line like this:

"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\CommonExtensions\Platform\Debugger\VsDebugConsole.exe" \\.\pipe\Microsoft-VisualStudio-Debug-Console-12068 Local\{8E165DED-A034-4002-8023-537D78849A4B} /RootProcessId:12068

As such it won't get matched. Should profiles with a relative path in the command line match the trailing end of the path in the incoming command line? I'm not sure it should...

[zadjii-msft]

Should profiles with a relative path in the command line match the trailing end of the path in the incoming command line? I'm not sure it should

I agree. @javierdlg can you take it up as a work item on the VS side to update that profile to specify the full path to VsDebugConsole.exe? You probably know better than us how to get that onto the VS backlog 😅

[silkfire]

Any update on this?