Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for locating Visual Studio Build Tools without an installation of the IDE #230

Closed
resiina opened this issue Feb 11, 2021 · 2 comments
Labels
duplicate wontfix By design or would break existing callers.

Comments

@resiina
Copy link

resiina commented Feb 11, 2021

I have only installed Visual Studio Build Tools, not the IDE itself, on a machine that automatically builds projects using the build tools. I'd like to be able to use this to find the Visual Studio Build Tools installation so that I would not need to change the path whenever I update the build system to a newer version of Visual Studio Build Tools.

Steps to reproduce issue:

  • Execute vswhere.exe on a machine that doesn't have Visual Studio IDE installed on it, just Visual Studio Build Tools

Expected behaviour:

  • vswhere.exe correctly locates the Visual Studio Build Tools directory, just like it does with an installation of Visual Studio IDE

Actual behaviour:

  • vswhere.exe does not locate any Visual Studio Build Tools installations
@heaths
Copy link
Member

heaths commented Feb 11, 2021

This is already supported. Please see #8. Basically,

vswhere -products *

This will find any product. By default, this was only meant to find instances of Visual Studio. Build Tools does not contain all the same features as Visual Studio.

@heaths heaths closed this as completed Feb 11, 2021
@heaths heaths added duplicate wontfix By design or would break existing callers. labels Feb 11, 2021
@daniol
Copy link

daniol commented Feb 15, 2021

I use the following to get the installation path:
vswhere -latest -products Microsoft.VisualStudio.Product.BuildTools -property installationPath

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate wontfix By design or would break existing callers.
Projects
None yet
Development

No branches or pull requests

3 participants