Was vswhere.exe supposed to find a "Build tools" install?

[brunomlopes]

On a build agent I installed the "Build tools for Visual Studio 2017" ( taken from https://www.visualstudio.com/downloads/ , under "Other Tools and Frameworks", "Build Tools for Visual Studio 2017" ).

Running vswhere doesn't find that install. Shouldn't it?

PS S:\temp> .\vswhere -latest -requires Microsoft.Component.MSBuild
Visual Studio Locator version 1.0.62 [query version 1.9.77.53636]
Copyright (C) Microsoft Corporation. All rights reserved.

PS S:\temp>

It does find the install for a "legacy" version, if that's relevant:

PS S:\temp> .\vswhere -legacy
Visual Studio Locator version 1.0.62 [query version 1.9.77.53636]
Copyright (C) Microsoft Corporation. All rights reserved.

instanceId: VisualStudio.10.0
installationPath: C:\Program Files (x86)\Microsoft Visual Studio 10.0\
installationVersion: 10.0
PS S:\temp>

[refack]

As of version 1.0.40 you can add -products * to include Buildtools in the search.
See last paragraph of https://github.com/Microsoft/vswhere/wiki/Find-MSBuild

[heaths]

As stated in the usage output and documentation herein, vswhere searches, by default, for Community, Professional, and Enterprise products. Build Tools and other products installed by the new Installer can by found either by passing in a comma-separated list of product IDs to -products or just specifying -products * as @refack mentioned.

[brunomlopes]

So sorry, I must have missed that. I wasn't considering BuildTools to be a product, but makes sense. Thanks for the responses.

…

On Tue, May 2, 2017 at 5:52 PM, Heath Stewart ***@***.***> wrote: As stated in the usage output and documentation herein, *vs*where searches, by default, for Community, Professional, and Enterprise products. Build Tools and other products installed by the new Installer can by found either by passing in a comma-separated list of product IDs to -products or just specifying -products * as @refack <https://github.com/refack> mentioned. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#61 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFEWsrY_Uqi8-53vWSAQCGf2M2yOMQ0ks5r119OgaJpZM4NOFZr> .

[uli-weltersbach]

Just to be clear, the reason why I'm not seeing any output on our build server is because the build tools were not installed with "the new installer"?
If so, what is "the new installer"?

[brunomlopes]

I think for 2015 and earlier you need to use "-legacy"

…

On Wed, May 31, 2017 at 8:33 AM, Uli Weltersbach ***@***.***> wrote: Just to be clear, the reason why I'm not seeing any output on our build server is because the build tools were not installed with "the new installer"? If so, what is "the new installer"? [image: vswhere exe and msbuild tools] <https://cloud.githubusercontent.com/assets/1416006/26620711/2f3a20cc-45e4-11e7-957a-70bd4921d8e8.png> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#61 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFEWllziaKOjLa0DYrWPuRucENLVUcRks5r_RfIgaJpZM4NOFZr> .

[uli-weltersbach]

Thanks for the quick response, but that still doesn't do the trick.
When using the "-legacy" flag I get a path to an old VS2012 installation, but still no luck on e.g. "C:\Program Files (x86)\MSBuild\14.0" :|

[heaths]

Because that is not a VS path. MSBuild was located under Visual Studio starting with 2017. It was in the same place under %ProgramFiles(x86)%\MSBuild before that. There are other ways to find MSBuild prior to 2017 that are outside the scope and purpose of vswhere.