![]() EditĪfter changing the Default terminal application to Windows Console Host, VS still fails to start debug with the exact same error. Signing-out/in helps, but again, only for the first time. Once you close the tab, debugging from VS won't work for terminal. No matter what option you have chosen for the New instance behavior. ![]() Once you log in you have 1 possibility to get the debug action work in the windows terminal. I did some experiments, and my findings are the following. Select Startup and choose 'Windows Terminal' as the Default terminal application setting. I tried to switch back the New instance behavior to Create a new window, but the error message remains there. Open Windows Terminal and go to the Settings UI window. ![]() So I head over to the settings and set the New instance behavior to Attach to the most recently used window and then tried to debug in VS and it started failing to start a terminal with an error code 0xc0000142. In the beginning it opened a new terminal window and started debugging there, which is fine, but I wanted it to open a new tab in the already open window. Then I set the Default terminal application to Windows Terminal Preview and started debugging in the Visual Studio 2022 (not sure if the version matters, I'm using Community edition). In my case, I installed the Preview version of the terminal today (it's version.
0 Comments
Leave a Reply. |