Visual Studio Setup

Installation and containerization of the Visual Studio family of products

Installation Archives - Page 2 of 25 - Visual Studio Setup

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

May 10, 2017 May 10, 2017 05/10/17
Heath Stewart
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 and ...

Documentation now live for moving or disabling the package cache

May 4, 2017 May 4, 2017 05/4/17
Heath Stewart
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 ...

vswhere is now installed with Visual Studio 2017

April 21, 2017 Apr 21, 2017 04/21/17
Heath Stewart
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 ...

Cleaning up the Visual Studio 2017 package cache

April 19, 2017 Apr 19, 2017 04/19/17
Heath Stewart
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 - perhaps scripting it for ...

Moving or disabling the package cache for Visual Studio 2017

April 17, 2017 Apr 17, 2017 04/17/17
Heath Stewart
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 in a few weeks - scheduled for ...

Documentation available for the Setup Configuration API

January 25, 2017 Jan 25, 2017 01/25/17
Heath Stewart
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 Visual Studio and related tools, or to install extensions. I previously published some samples...

Changes to Visual Studio “15” Setup

September 15, 2016 Sep 15, 2016 09/15/16
Heath Stewart
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 Studio "15...

Get the Windows Installer PowerShell Module easier with WMF 5.0

December 18, 2015 Dec 18, 2015 12/18/15
Heath Stewart
Many years ago when PowerShell was first in beta, I saw an opportunity to write cmdlets that I could string together in different ways rather than writing and maintaining a bunch of one-off Windows scripts for various day-to-day tasks and customer diagnostics. I created the Windows Installer PowerShell Module to fill that role. These cmdlets ...

Removing Visual Studio components left behind after an uninstall

July 17, 2015 Jul 17, 2015 07/17/15
Heath Stewart
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 ...