System Requirements

1 minute read

Supported Visual Studio Versions

The Visual Studio IDE Integration supports the following versions of Visual Studio:

  • Visual Studio 2017 (all editions)

  • Visual Studio 2015

  • Visual Studio 2013

  • Visual Studio 2012

  • Visual Studio 2010

  • Visual Studio 2008

  • Visual Studio 2005 (command-line only)

The Visual Studio IDE Converter for Visual Studio 2010 or later does not support Xbox builds, Windows Mobile configurations, or custom build rules.

Prerequisites

MSBuild Prerequisites

The IDE converter cannot virtualize the MSBuild utility. If you are virtualizing your toolchain, you might need to install the following packages for your version of Visual Studio on every agent host in your cluster.

Visual Studio Version Packages

2017

*.NET Framework 4.6.2 * MSBuild Tools 15.0 * Visual C++ Build Tools 15.0

2015

*.NET Framework 4.6 * Microsoft Build Tools 2015

2013

*.NET Framework 4.5 * Microsoft Build Tools 2013

2012

2010

2008

2005

If you do not virtualize your toolchain, you must install Visual Studio on each agent host in your cluster.

Visual Studio IDE Extension Prerequisites

The Visual Studio IDE extension requires:

  • Accelerator installed on the build machine *.NET Framework v2.0

Visual Studio Converter Extension Prerequisites

The Visual Studio Converter Extension requires:

  • Microsoft Visual C++ 2010 Redistributable Package *.NET Framework v2.0

  • (If using Visual Studio 2005 Service Pack 1) Microsoft hotfix that is described in Microsoft Knowledge Base articles 933054 and 934517. Without the hotfix, the Visual Studio Converter Add-In will not function correctly, which means that ecdevenv is not called, so builds will not be accelerated.

ecdevenv Utility Prerequisites

The ecdevenv utility requires:

  • Visual Studio Converter Extension *.NET Framework v2.0

Electrify Utility Prerequisites

The Electrify utility requires the Microsoft Visual C++ 2005 SP1 Redistributable Package.

Upgrade Notes

CloudBees recommends regenerating the history file after upgrading the Visual Studio Integration.