Home → Questions →

`vswhere` on AppVeyor?

• Edit

Jan Pio

13 Feb, 2018 03:51 PM

Has anyone successfully used`vswhere on AppVeyor to output the path to the VS or MSBuild installation?

Locally I can run it like this:

λ "%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere" -property installationPath -all
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community

But on AppVeyor I get this:

"%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere" -property installationPath -products * -all
The system cannot find the path specified.

1. 1 Posted by Ilya Finkelshte... on 13 Feb, 2018 06:05 PM

   

   It is not included into build worker VM. You can easily download it from GitHub releases and run, like this:

   - appveyor DownloadFile https://github.com/Microsoft/vswhere/releases/download/2.3.2/vswhere.exe
   - vswhere.exe
   

   However for me simple command like where msbuild should be good enough.

   • Edit

2. 2 Posted by Jan Pio on 13 Feb, 2018 08:25 PM

   

   Oh interesting. I thought this was part of every modern Visual Studio 2017 installation now. Do you manually remove it or is this just not part of the type of installation you are doing?

   (Good to know, we actually wanted to rely on that program in the VS17 version of our tooling)

   • Edit

3. 3 Posted by Ilya Finkelshte... on 13 Feb, 2018 08:41 PM

   

   No it, it just not part of VS 2017 Community. I believe it is part of Build Tools for Visual Studio 2017 which we do not install.

   • Edit

4. 4 Posted by Jan Pio on 13 Feb, 2018 11:34 PM

   

   Uhhh... actually it is installed:

   "%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere" -property installationPath -products * -all
   C:\Program Files (x86)\Microsoft Visual Studio\2017\Community
   C:\Program Files (x86)\Microsoft Visual Studio\2017\TestAgent
   "%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere" -property installationPath -all
   C:\Program Files (x86)\Microsoft Visual Studio\2017\Community
   

   (Aso checked locally, comes with the Installer of VS2017 Community itself)

   Better question now: Did I mess up before or did it really not work before?

   Update: Indeed, I looked at the VS15 runs where vswhere of course is missing. Sorry.

   • Edit

5. 5 Posted by Ilya Finkelshte... on 14 Feb, 2018 07:10 PM

   

   Thanks for letting us know, indeed it is there now :)

   • Edit

6. Jan Pio closed this discussion on 14 Feb, 2018 07:25 PM.