Read about all the new properties output by vswhere.
Follow this guidance to install Build Tools for Visual Studio 2017 into a Docker container and save the image for later.
When older versions of Visual Studio 2017 report an error about not being able to load the instance, follow these instructions to clean up corrupt instances and re-install.
A new major version of vswhere is released with the breaking change to filter out preview releases by default.
With the release of Visual Studio 2017 version 15.2, the ability to disable or move the package cache is now generally available and documented. Basically, payloads are removed after being installed or repaired, and we will download them again if ever needed (like when repairing the product instance).
I previously wrote about moving or disabling the package cache for Visual Studio 2017, which is a feature in the latest preview of Visual Studio 2017 and will be generally available update 15.2 is released.
We have now published the documentation along with related material for administrators or developers looking to take more control of their installations,
Starting in the latest preview release of Visual Studio version 15.2 (26418.1-Preview), you can now find vswhere installed in “%ProgramFiles(x86)%\Microsoft Visual Studio\Installer” (on 32-bit operating systems before Windows 10, you should use “%ProgramFiles%\Microsoft Visual Studio\Installer”).
While I initially made vswhere.exe available via NuGet and Chocolatey for easy acquisition,
With the ability to disable or move the package cache for Visual Studio 2017 and other products installed with the new installer, packages are removed for whatever instance(s) you are installing, modifying, or repairing.
If you have a lot of instances and want to clean all of them up easily from the command line –
In the latest preview release of Visual Studio we are introducing the ability to disable (or re-enable) the package cache, or move it to another drive. This can be done using the command line or the registry, which can be deployed on a domain using group policy.
One of the top requests I kept hearing for vswhere was to also search older versions of Visual Studio. You can now do that starting with the latest release.
vswhere -legacy -latest -property installationPath
Even if you don’t have Visual Studio 2017 or newer installed –
Four years ago I published a utility to help perform a clean uninstall of Visual Studio 2010. Before we added package reference counting and related bundles to Visual Studio setup, we couldn’t always be sure which products were still required so not everything was removed.
Add a .vsconfig file to your solution root directory to configure Visual Studio consistently across your organization.
If you try to install Build Tools for Visual Studio 2017 into a Windows Server 2019 or newer container image, such as mcr.microsoft.com/windows/servercore:1809 or mcr.microsoft.com/windows/servercore:ltsc2019, the install will quickly terminate without error and without installing anything. This is due, in part,
We are investigating how a particular rare problem occurs that can prevent clients like VSIXInstaller.exe, vswhere.exe, and others from finding any Visual Studio instance that results in an error similar to the following:
This is the CLSID for the Visual Studio Installer query API,
Use or contribute your own Dockerfiles on GitHub to help others build similar workloads with Visual Studio Build Tools.
The size and permutations of Build Tools 2017 container images are too great to publish official images, but here's how you can create your own tailored images.
You can now force vswhere to output JSON using the UTF-8 encoding.
The .NET Framework may not be correctly installed into a Windows Server Core container, and managed code - like the compilers - may fail. The documentation was updated with how to work around this.
You can now use -requiresAny with vswhere to specify that any component ID passed to -requires will satisfy the query.
Due to a bug in older versions of Visual Studio 2017, you should set the CachePath policy in both 32- and 64-bit views of the registry.
Preview new documentation for how to install Build Tools for Visual Studio 2017 into a Docker container.