Description of the new feature / enhancement
The output of the install and uninstall commands is very much meant for interactive execution within a terminal. But for automation, viewing the output of these commands in the automation logs is ugly.
Here's some example from a build machine running dotnet install:
2022-04-06T18:57:55.7057087Z Downloading https://dotnetcli.azureedge.net/dotnet/aspnetcore/Runtime/3.1.23/aspnetcore-runtime-3.1.23-win-x64.exe
2022-04-06T18:57:57.2410537Z �-�\�|�
2022-04-06T18:57:57.2410978Z
2022-04-06T18:57:57.2411667Z ██████████████████████████████ 7.66 MB / 7.66 MB
2022-04-06T18:57:57.2412406Z Successfully verified installer hash
2022-04-06T18:57:57.7536340Z �-�
2022-04-06T18:57:57.7537168Z Starting package install...
2022-04-06T18:58:03.6942082Z �-�\�|�/�-�\�|�/�-�\�|�/�-�\�|�/�-�\�|�/�-�\�
2022-04-06T18:58:03.6944725Z Successfully installed
2022-04-06T18:58:04.1768766Z �-�
2022-04-06T18:58:04.1769928Z Executing uninstall for Microsoft.DotNet.AspNetCore.3_1
2022-04-06T18:58:04.1774310Z
2022-04-06T18:58:05.3501883Z �-�\�
2022-04-06T18:58:05.9925470Z �-�
Can this get cleaned up a bit to allow for better output in noninteractive scenarios?
Proposed technical implementation details
No response
Description of the new feature / enhancement
The output of the
installanduninstallcommands is very much meant for interactive execution within a terminal. But for automation, viewing the output of these commands in the automation logs is ugly.Here's some example from a build machine running
dotnet install:Can this get cleaned up a bit to allow for better output in noninteractive scenarios?
Proposed technical implementation details
No response