Sort by:

Cleaning up corrupt Visual Studio instances

by Heath Stewart (MSFT) // 0 Comments

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

vswhere version 2.0 released

by Heath Stewart (MSFT) // 0 Comments

One of the features of the new setup engine is to enable Visual Studio to be installed side-by-side with other minor releases, including minor upgrades and preview releases. After introducing the Visual Studio Preview channel a short while ago, some partners asked for the ability to filter out those Preview releases from vswhere.exe. Because this is… Read more

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

by Heath Stewart (MSFT) // 2 Comments

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

by Heath Stewart (MSFT) // 0 Comments

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

by Heath Stewart (MSFT) // 8 Comments

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

by Heath Stewart (MSFT) // 0 Comments

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

by Heath Stewart (MSFT) // 11 Comments

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

vswhere now searches older versions of Visual Studio

by Heath Stewart (MSFT) // 4 Comments

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. Even if you don’t have Visual Studio 2017 or newer installed – which means the query API is not even registered – you can use vswhere… Read more

Fast acquisition of vswhere

by Heath Stewart (MSFT) // 0 Comments

I introduced vswhere last week as an easy means to locate Visual Studio 2017 and newer, along with other products installed with our new installer that provides faster downloads and installs – even for full installs (which has roughly doubled in size with lots of new third-party content). vswhere was designed to be a fast,… Read more

vswhere Available

by Heath Stewart (MSFT) // 5 Comments

After feedback on the VSSetup PowerShell module to query Visual Studio 2017 and related products, I’m pleased to say that a native, single-file executable is available on GitHub: vswhere. The VSSetup PowerShell module is also available on GitHub and provides a number of benefits for PowerShell scripts, but build tools and CMake and deployment scripts… Read more