|
| 1 | +--- |
| 2 | +title: "Import or export installation configurations" |
| 3 | +titleSuffix: "" |
| 4 | +description: "Learn how to use the import/export configuration feature in Visual Studio" |
| 5 | +ms.date: 04/15/2019 |
| 6 | +ms.topic: conceptual |
| 7 | +f1_keywords: |
| 8 | + - "vs.about" |
| 9 | +helpviewer_keywords: |
| 10 | + - "import installation configuration" |
| 11 | + - "export installation configuration" |
| 12 | + - "install Visual Studio" |
| 13 | + - "Visual Studio installer" |
| 14 | +author: TerryGLee |
| 15 | +ms.author: tglee |
| 16 | +manager: jillfra |
| 17 | +ms.workload: |
| 18 | + - "multiple" |
| 19 | +ms.prod: visual-studio-windows |
| 20 | +ms.technology: vs-installation |
| 21 | +--- |
| 22 | +# Import or export installation configurations |
| 23 | + |
| 24 | +You can configure Visual Studio across your organization by using an installation configuration file. To do so, simply export the workload and component information to a .vsconfig file by using the Visual Studio installer. You can then import the configuration into new or existing installations. |
| 25 | + |
| 26 | +Here's how. |
| 27 | + |
| 28 | +::: moniker range="vs-2017" |
| 29 | + |
| 30 | +> [!NOTE] |
| 31 | +> This functionality is available only in Visual Studio 2017 version 15.9 and later. |
| 32 | +
|
| 33 | +::: moniker-end |
| 34 | + |
| 35 | +## Export a configuration |
| 36 | + |
| 37 | +You can choose to export an installation configuration file from either a previously installed instance of Visual Studio or one that you're currently installing. |
| 38 | + |
| 39 | +1. Open the Visual Studio Installer. |
| 40 | + |
| 41 | +1. On the product card, choose the **More** button, and then select **Export configuration**. |
| 42 | + |
| 43 | +1. Browse to or type the location where you want to save your .vconfig file, and then choose **Review details**. |
| 44 | + |
| 45 | +  |
| 46 | + |
| 47 | +1. Make sure you've got the workloads and components that you want, and then choose **Export**. |
| 48 | + |
| 49 | +## Import a configuration |
| 50 | + |
| 51 | +When you're ready to import an installation configuration file |
| 52 | + |
| 53 | +1. Open the Visual Studio Installer. |
| 54 | + |
| 55 | +1. On the product card, choose the **More** button, and then select **Import configuration**. |
| 56 | + |
| 57 | +1. Locate the .vconfig file that you want to import, and then choose **Review details**. |
| 58 | + |
| 59 | +1. Make sure you've got the workloads and components that you want, and then choose **Close**. |
| 60 | + |
| 61 | +::: moniker range="vs-2019" |
| 62 | + |
| 63 | +## Automatically install missing components |
| 64 | + |
| 65 | +**New in Visual Studio 2019**: When you save a .vsconfig file to your solution root directory and then open a solution, Visual Studio automatically detects which components are missing and prompts you to install them. |
| 66 | + |
| 67 | + |
| 68 | + |
| 69 | +You can also generate a .vsconfig file right from Solution Explorer. Here's how. |
| 70 | + |
| 71 | +1. Right-click on your solution file. |
| 72 | + |
| 73 | +1. Choose **Add** > **Installation Configuration File**. |
| 74 | + |
| 75 | +1. Confirm the location where you want to save the .vsconfig file, and then choose **Review details**. |
| 76 | + |
| 77 | +1. Make sure you've got the workloads and components that you want, and then choose **Export**. |
| 78 | + |
| 79 | +::: moniker-end |
| 80 | + |
| 81 | +> [!NOTE] |
| 82 | +> For more information, see the [Configure Visual Studio across your organization with .vsconfig](https://devblogs.microsoft.com/setup/configure-visual-studio-across-your-organization-with-vsconfig/) blog post. |
| 83 | +
|
| 84 | +[!INCLUDE[install_get_support_md](includes/install_get_support_md.md)] |
| 85 | + |
| 86 | +## See also |
| 87 | + |
| 88 | +* [Create a network installation of Visual Studio](create-a-network-installation-of-visual-studio.md) |
| 89 | +* [Update a networked-based installation of Visual Studio](update-a-network-installation-of-visual-studio.md) |
| 90 | +* [Control updates to Visual Studio deployments](controlling-updates-to-visual-studio-deployments.md) |
| 91 | +* [Set defaults for enterprise deployments](set-defaults-for-enterprise-deployments.md) |
0 commit comments