Jonathan Dodds
Jonathan Dodds
@YuliiaKovalova Tested/validated and confirmed that the issue is resolved. Thanks
@orehmane Just to provide some background detail that may help: A solution file (.sln) is not an MSBuild file. When a solution file is passed to MSBuild, MSBuild creates a...
@rainersigwald Thanks for the correction.
I use the equivalent of the following: ```zsh # Unsupported dotnet-core-uninstall dry-run --major-minor 7.0 --runtime dotnet-core-uninstall dry-run --major-minor 7.0 --sdk dotnet-core-uninstall dry-run --major-minor 6.0 --runtime dotnet-core-uninstall dry-run --major-minor 6.0 --sdk...
The dotnet uninstall tool is supported in WinGet for Windows.
Please assign this issue to me. Thanks
More than just supporting `cmd`, I'd like the equivalent of the "Developer Command Prompt for Visual Studio" to be supported which means launching `cmd` with a `/k` option to run...
@RokeJulianLockhart, Portability/usability across OSes is not relevant to this issue. No one expects `cmd.exe` to be supported on an OS other than Windows. Also see [Microsoft/Terminal](https://github.com//microsoft/terminal) as a starting point...
The initial request includes: > I would like for Warp on Windows to support [Cmd.exe](https://en.wikipedia.org/wiki/Cmd.exe). Running `cmd` from another shell is not Warp supporting `cmd`. (It is also not useful...
I have reports that are generated by MSBuild with -v:n and the `Message` task that are only sometimes redirected to a file. To get text output of my messages I...