MSBuild Structured Log Viewer is a logger for MSBuild that records a structured representation of executed targets, tasks, property and item values. It can greatly simplify build investigations and provides a portable log interchange format and a rich interactive log viewer app. This article will serve as an informative guide and give you a clear understanding of how to perform a silent installation of MSBuild Structured Log Viewer from the command line using the EXE installer.
How to Install MSBuild Structured Log Viewer Silently
MSBuild Structured Log Viewer Silent Install (EXE)
- Navigate to: https://github.com/KirillOsenkov/MSBuildStructuredLog/releases/latest
- Download the MSBuildStructuredLogSetup.exe to a folder created at (C:\Downloads)
- Open an Elevated Command Prompt by Right-Clicking on Command Prompt and select Run as Administrator
- Navigate to the C:\Downloads folder
- Enter the following command: MSBuildStructuredLogSetup.exe -s
- Press Enter
After a few moments you will find MSBuild Structured Log Viewer entries in the Start Menu, Installation Directory, and Programs and Features in the Control Panel.
| Software Title: | MSBuild Structured Log Viewer |
| Vendor: | Kirill Osenkov |
| Architecture: | x86_x64 |
| Installer Type: | EXE |
| Silent Install Switch: | MSBuildStructuredLogSetup.exe -s |
| Silent Uninstall Switch: | "%LocalAppData%\MSBuildStructuredLogViewer\Update.exe" --uninstall -s |
| Download Link: | https://github.com/KirillOsenkov/MSBuildStructuredLog/releases/latest |
The information above provides a quick overview of the software title, vendor, silent install, and silent uninstall switches. The download links provided take you directly to the vendors website.
How to Uninstall MSBuild Structured Log Viewer Silently
- Open an Elevated Command Prompt by Right-Clicking on Command Prompt and select Run as Administrator
- Enter the following command:
MSBuild Structured Log Viewer Silent Uninstall (EXE)
"%LocalAppData%\MSBuildStructuredLogViewer\Update.exe" --uninstall -s |
Always make sure to test everything in a development environment prior to implementing anything into production. The information in this article is provided “As Is” without warranty of any kind.
