Visual Studio Setup

Installation and containerization of the Visual Studio family of products

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,

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,

Uncategorized

Older versions of Visual Studio 2017 will not install in Windows Server 2019 containers

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,

Workaround for 0x8007007e when trying to to locate an instance of Visual Studio

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:

Retrieving the COM class factory for component with CLSID {177F0C4A-1CD3-4DE7-A32C-71DBBB9FA36D} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E).

This is the CLSID for the Visual Studio Installer query API,

Docker recipes available for Visual Studio Build Tools

Use or contribute your own Dockerfiles on GitHub to help others build similar workloads with Visual Studio Build Tools.

No container image for Build Tools for Visual Studio 2017

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.

vswhere now supports -utf8 to override console code page

You can now force vswhere to output JSON using the UTF-8 encoding.

Updated documentation for Visual Studio Build Tools container

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.

vswhere now supports -requiresAny to find instances with one or more components installed

You can now use -requiresAny with vswhere to specify that any component ID passed to -requires will satisfy the query.

Set both x86 and x64 registry views for custom setup policy

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.

How to install Builds Tools in a Docker container

Preview new documentation for how to install Build Tools for Visual Studio 2017 into a Docker container.

New vswhere: now with more properties!

Read about all the new properties output by vswhere.