This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

✅ Build vswhere 1.0.18-beta+g7867f84655 completed (commit 7867f84655 by @refack)

Should also mention that the defaults are VS because that is the main use case for vswhere.

IMHO you should add 'BuildTools' as a use case since that would make vswhere a welcome companion to the "CLI" compatible tool-set.

It is. Pass it to the -products command line switch. New version with -help support and more just went up.

The installer installs lots of products and more will be added. The default use case is VS (very different composition than built tools) but it was always my goal to support all products, hence the switch.

I still think vswhere not finding the build tools is the wrong approach. I want to move away from VS2015 but vswhere brakes the command line tools for CMake for me in the CI.

It wasn't necessary when originally spec'd, and Build Tools back then was missing a lot of tools (compilers, etc.) that VS had. Changing what it detects after it had been out for a long time would be a breaking change to many build systems, hence having to opt into detecting it which you can easily do with the -products parameter.

To reiterate before I close this thread: we cannot responsibility change the detection to include Build Tools by default or it will be a breaking behavioral change.