Tags: microsoft/vswhere
Tags
Release new version of vswhere (#259) * Update docker image (#240) * Update microbuild pool to VS2019 * Use correct pool name * Update docker images * Colorize vswhere output (#244) * Refactor formatters to consolidate arguments * Colorize output by default unless piped * Opt into color and add tests Fails in PowerShell if you do something like `[xml](vswhere -format xml)` if color is enabled, so had to add -color switch. Not ideal since it otherwise disables color when piped, but still easier to read if colorized explicitly. * Enable colors by default, add -nocolor switch * Resolve PR feedback * Ensure console is initialized Could simply call Initialize wherever it needs to be called, but would rather be explicit. * Update AzDO build to use new 1ES pool * Add compliance build * Update targeting to Windows 7 * Enable ControlFlowGuard * Fix Prefast errors in source * Fix test prefast issues * Update to latest cached docker image * Suppress individual prefast warnings for fallthrough cases * FIxup comments for variants * Upgrade agent to Server 2019 with VS2019 (#260) Co-authored-by: Laurel Williams <20650063+lwillia@users.noreply.github.com> Co-authored-by: Davi Paulino <dalimapa@microsoft.com> Co-authored-by: Davi Paulino <davilimap@gmail.com> Co-authored-by: Tyler Dunkel <40210514+tydunkel@users.noreply.github.com>
Colorize vswhere output (#244) * Refactor formatters to consolidate arguments * Colorize output by default unless piped * Opt into color and add tests Fails in PowerShell if you do something like `[xml](vswhere -format xml)` if color is enabled, so had to add -color switch. Not ideal since it otherwise disables color when piped, but still easier to read if colorized explicitly. * Enable colors by default, add -nocolor switch * Resolve PR feedback * Ensure console is initialized Could simply call Initialize wherever it needs to be called, but would rather be explicit.
PreviousNext