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

Using VSWhere to identify VS installation #2

Closed
tomachristian opened this issue Aug 24, 2017 · 1 comment
Closed

Using VSWhere to identify VS installation #2

tomachristian opened this issue Aug 24, 2017 · 1 comment

Comments

@tomachristian
Copy link

I had problems with corrupted VS installations and the install_script did not detect the installation folder properly. I had to install it manually.

An interesting ideea would be to use VSWhere to identify the VS installations and their paths.

@Sibras
Copy link
Member

Sibras commented Aug 28, 2017

Thanks for the suggestion, Detecting VS installs is a difficult problem and something that needs to be improved in the install script (which is only a lightweight installer). VSWhere may provide a solution. Although adding an external install dependency does complicate things. But this may be something i keep in mind for a future update.

Sibras added a commit that referenced this issue Jan 28, 2019
Supports vswhere, multiple installation detection and VS2019 support.

closes #3  #2
@Sibras Sibras closed this as completed May 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants