vswhere now searches older versions of Visual Studio

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

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

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

Visual Studio Setup PowerShell Module Available

To make the new setup configuration APIs more accessible to developers, we have published the “VSSetup” PowerShell module on powershellgallery.com, making it quick and easy to install. If you have Windows Management Framework (WMF) 5.0 or newer – installed with Windows 10 – or PowerShellGet for PowerShell 3.0 or 4.0, you can run the following… Read more

Documentation available for the Setup Configuration API

Visual Studio 2017 has brought big changes to extensibility that allow developers to install extensions to different instances and install dependencies. In support of multiple instances, a fast API was required that tools can use to find and launch VS and related tools, or to install extensions. I previously published some samples, and now documentation… Read more

Changes to Visual Studio “15” Setup

We’ve listened to feedback over the years, and while each new release brought changes to the setup experience of Visual Studio and related products, none have been more significant than what we’re doing for Visual Studio “15”. New setup engine With Visual Studio supporting so many platforms and toolkits, one of the goals for Visual… Read more

Failure when upgrading from VS2015 RTM to VS2015 with Update 1

If you have Visual Studio 2015 RTM installed and attempt to install Visual Studio 2015 with Update 1, you may see a failure like the screenshot that reads, KB3022398 This action is only valid for products that are currently installed. This is a fatal error that occurs when upgrading from VS 2015 RTM to the… Read more

Removing Visual Studio components left behind after an uninstall

When you install Visual Studio and related content like Windows Kits or some add-ons, most packages that comprise those bundles are reference counted to make sure they are not removed prematurely. Uninstalling Visual Studio and related content should eventually remove those packages (i.e. last one out the door turns off the light). Contrast with older… Read more

How to install Visual Studio to another directory when a pre-release is installed

If you’ve installed pre-release versions of Visual Studio – or even another edition of the same release – you may find you can’t change the installation target directory. This is because once a set of shared components is installed, we install all the other components to the same directory structure. When you have multiple editions… Read more

Redirect the Package Cache using registry-based policy

Visual Studio can require a lot of space on the system drive, and previous methods of redirecting the Package Cache can be tricky for some people to set up or even maintain as junctions across volumes may be removed on boot. The cache is there for good reasons and has significantly reduced the failure rate,… Read more