Visual Studio 2017 workload and component IDs
Click the edition names in the following table to see the available workload and component IDs you need to install Visual Studio by using a command line, or to specify as a dependency in a VSIX manifest.
|Visual Studio Enterprise 2017||Microsoft.VisualStudio.Product.Enterprise||Microsoft DevOps solution for productivity and coordination across teams of any size|
|Visual Studio Professional 2017||Microsoft.VisualStudio.Product.Professional||Professional developer tools and services for small teams|
|Visual Studio Community 2017||Microsoft.VisualStudio.Product.Community||Free, fully featured IDE for students, open-source, and individual developers|
|Visual Studio Team Explorer 2017||Microsoft.VisualStudio.Product.TeamExplorer||Interact with Team Foundation Server and Visual Studio Team Services without a Visual Studio developer toolset|
|Visual Studio Desktop Express 2017||Microsoft.VisualStudio.Workload.WDExpress||Build Native and Managed applications like WPF, WinForms, and Win32 with syntax-aware code editing, source code control, and work item management. Includes support for C#, Visual Basic, and Visual C++.|
|Visual Studio Build Tools 2017||Microsoft.VisualStudio.Product.BuildTools||The Visual Studio Build Tools allows you to build native and managed MSBuild-based applications without requiring the Visual Studio IDE. There are options to install the Visual C++ compilers and libraries, MFC, ATL, and C++/CLI support.|
|Visual Studio Test Agent 2017||Microsoft.VisualStudio.Product.TestAgent||Supports running automated tests and load tests remotely|
|Visual Studio Test Controller 2017||Microsoft.VisualStudio.Product.TestController||Distribute automated tests to multiple machines|
|Visual Studio Test Professional 2017||Microsoft.VisualStudio.Product.TestProfessional||Visual Studio Test Professional 2017|
|Visual Studio Feedback Client 2017||Microsoft.VisualStudio.Product.FeedbackClient||Visual Studio Feedback Client 2017|
For more information about how to use these lists, see the Use command-line parameters to install Visual Studio 2017 page and the How to: Migrate extensibility projects to Visual Studio 2017 page.
Sometimes, things can go wrong. If your Visual Studio installation fails, see the Troubleshooting Visual Studio 2017 installation and upgrade issues page for troubleshooting tips. As well, you can report product issues to us via the Report a Problem tool in the Visual Studio IDE or share a suggestion with us on UserVoice. You can track product issues in the Visual Studio Developer Community, and ask questions and find answers. You can also engage with us and other Visual Studio developers through our Visual Studio conversation in the Gitter community (requires a GitHub account).