Heath Stewart

@lmazuel can you help merge this? The breaking changes are expected.

@weshaggard all the `error` errors are expected. At one point they made `error` required as it always should've been. I'm actually surprised they're still seeing this since - at least...

``` $ winget show Microsoft.VisualStudio.Locator Found Visual Studio Locator [Microsoft.VisualStudio.Locator] Version: 3.0.3.9285 Publisher: Microsoft Corporation Moniker: vswhere Description: Find and get information on Visual Studio versions 2017 and newer with...

Thanks for the heads up. I updated that page.

This is the documented behavior and consistent with VSIXInstaller version ranges. A single version means [17,). Not to mention, changing this would be a breaking change for anyone looking for,...

If anything, perhaps we can expand on the version syntax or at least link to https://github.com/microsoft/vswhere/wiki/Examples (maybe add a heading directly for version syntax, or add a new page and...

@bergmeister, GUIDs aren't necessary *most* times, and WiX recommends against them. I removed the GUIDs because, when the path changes ("7" vs. "7-preview"), having the same GUID ref-counts different files/registry...

> * Operation/property not supported in api-version=**x**; operation/property was added in api-version=**y**. But isn't that necessary for other discussions like ignoring and not returning models/properties for API versions that don't...

@DHowett, @mislav for truecolor-detection support, is [this](https://github.com/cli/cli/blob/e6ff77ce73c201b0ee36d2b802ea45e9e1ad1822/pkg/iostreams/color.go#L36-L50) really the right detection then? There's mention of many different `TERM` values that wouldn't match these checks. Seems `TERM` has become grossly overloaded...

With [that](https://github.com/microsoft/terminal/issues/11057#issuecomment-908496636) in mind, it really seems like there's no good solution since the CLI supports pre-Windows 10 as do many apps out there. So would just trying to emit...