Set both x86 and x64 registry views for custom setup policy

I previously blogged about the documentation to move the Visual Studio 2017 package cache by changing the CachePath policy. Originally this was done only with changes under the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\VisualStudio\Setup registry key, which is defined under the usual location for server and application policies. This registry key is shared (formerly reflected) across both 32- and 64-bit… Read more

How to install Builds Tools in a Docker container

After working through a few issues, we have posted how to install Visual Studio Build Tools 2017 into a Docker container. A Build Tools container can be very useful for continuous integration / continuous delivery (CI/CD) scenarios. You can also use these same steps for Visual Studio if Build Tools does not currently have everything… Read more

New vswhere: now with more properties!

The latest release of vswhere now outputs additional properties as requested, along with catalog properties and a way to disambiguate nested properties – not that there are any currently. You can specify the nested properties followed by a property name like “properties/nickname”. Delimiters supported are “_”, “/”, and “.” to fit with the text, JSON,… Read more

Installing Build Tools for Visual Studio 2017 in a Docker container

Docker containers are a lightweight alternative to full virtual machines that abstract the file system of the host operating system but are otherwise isolated. While popular for service deployments as a complete means of acquisition, containers are also useful for isolating build and test environments. You can install Visual Studio 2017 and the Build Tools… Read more

Cleaning up corrupt Visual Studio instances

A small number of users are seeing errors after installing or modifying Visual Studio 2017 like the following, Sorry, the installation failed. Please try again. This may also manifest in some cases as, A product matching the following parameters cannot be found: channelId: VisualStudio.15.Release productId: Microsoft.VisualStudio.Product.Enterprise If you open the latest %TEMP%\dd_client*.log file you may… Read more

Disabling or moving the Visual Studio 2017 package cache is now generally available

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). This does mean if you work offline… Read more

Documentation now live for moving or disabling the package cache

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… Read more

vswhere is now installed with Visual Studio 2017

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, some projects do not use package managers… Read more

Cleaning up the Visual Studio 2017 package cache

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 –… Read more

Moving or disabling the package cache for Visual Studio 2017

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. This will be generally available in Visual Studio… Read more