But even the full path fails when the command is actually run. You can't just use the global wt.exe without a path (as you can with say explorer.exe or cmd.exe, so I have to provide the full path. Not really sure what the problem is, but it has something to do how Visual Studio launches executables. I can find the binary here:īut if I try to launch that in Visual Studio I get: Windows Terminal is a tricky tool to launch on External Tools, because the main executable wt.exe is an alias that launches the real binary. Launching Windows Terminal From Visual Studio External Tools I use a bunch of External Commands in Visual Studio (and also in Rider and WebStorm) to execute external tasks and tie them to menu hotkeys (ie.
Long story short for one of my builds - Markdown Monster in particular - I need to run the terminal as an admin. I need it for a couple of build tasks - Chocolatey installs of an admin install and for a funky certificate that doesn't want to work from the User certificate store. This isn't the first time I've talked about this, and probably won't be the last, but for my work in Visual Studio I often need an Admin Windows terminal window.
0 kommentar(er)
