Visual Studio 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.
Updated for the 16.11 release
Edition | ID | Description |
---|---|---|
Visual Studio Enterprise 2019 | Microsoft.VisualStudio.Product.Enterprise | Microsoft DevOps solution for productivity and coordination across teams of any size |
Visual Studio Professional 2019 | Microsoft.VisualStudio.Product.Professional | Professional developer tools and services for small teams |
Visual Studio Community 2019 | Microsoft.VisualStudio.Product.Community | Free, fully featured IDE for students, open-source, and individual developers |
Visual Studio Team Explorer 2019 | Microsoft.VisualStudio.Product.TeamExplorer | Interact with Team Foundation Server and Azure DevOps Services without a Visual Studio developer toolset |
Visual Studio Build Tools 2019 | 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 2019 | Microsoft.VisualStudio.Product.TestAgent | Supports running automated tests and load tests remotely |
Visual Studio Load Test Controller 2019 | Microsoft.VisualStudio.Product.TestController | Distribute automated tests to multiple machines |
For more information about how to use these lists, see the Use command-line parameters to install Visual Studio page and the How to: Migrate extensibility projects to Visual Studio page.
Note
For a list of the workload and component IDs for the previous version, see Visual Studio 2017 workload and component IDs
Updated for the 17.12 release
Edition | ID | Description |
---|---|---|
Visual Studio Enterprise 2022 | Microsoft.VisualStudio.Product.Enterprise | Microsoft DevOps solution for productivity and coordination across teams of any size |
Visual Studio Professional 2022 | Microsoft.VisualStudio.Product.Professional | Professional developer tools and services for small teams |
Visual Studio Community 2022 | Microsoft.VisualStudio.Product.Community | Free, fully featured IDE for students, open-source, and individual developers |
Visual Studio Team Explorer 2022 | Microsoft.VisualStudio.Product.TeamExplorer | Interact with Team Foundation Server and Azure DevOps Services without a Visual Studio developer toolset |
Visual Studio Build Tools 2022 | 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 2022 | Microsoft.VisualStudio.Product.TestAgent | Supports running automated tests and load tests remotely |
Visual Studio Load Test Controller 2022 | Microsoft.VisualStudio.Product.TestController | Distribute automated tests to multiple machines |
For more information about how to use these lists, see the Use command-line parameters to install Visual Studio page and the Update a Visual Studio extension for Visual Studio 2022 page.
Note
For a list of the workload and component IDs for the previous version, see Visual Studio 2019 workload and component IDs
Support or troubleshooting
Sometimes, things can go wrong. If your Visual Studio installation fails, see Troubleshoot Visual Studio installation and upgrade issues for step-by-step guidance.
Here are a few more support options:
- Use the installation chat (English only) support option for installation-related issues.
- Report product issues to us by using the Report a Problem tool that appears both in the Visual Studio Installer and in the Visual Studio IDE. If you're an IT Administrator and don't have Visual Studio installed, you can submit IT Admin feedback.
- Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.