Skip to main content

Visual Studio–Share your settings

In VSCode you can share your settings through profiles. This allows you to easily apply your UI layout, settings and extensions to multiple VSCode instances.

A similar thing is possible in Visual Studio. Settings can be exported through the Import and Export Settings Wizard:

  • Go to Tools –> Import and Export Settings
  • Choose Export selected environment settings and click on Next >
  • Now you can choose which settings should be exported. Check or uncheck the settings you want to export and click on Next >
  • Specify where you want to store your .vssettingsfile file and click on Finish
  • You can now close the wizard.

Remark: When you sign in to Visual Studio on multiple computers using the same personalization account, your settings can be synchronized across the computers.

Although the .vssettings file allows you to share a lot of configuration settings, it cannot be used to share the installed features and extensions. However this is possible through an installation configuration file(.vsconfig) and the Visual Studio Installer.

  • To export a configuration open the Visual Studio Installer
  • Click on More on the product card and choose Export configuration
  • Specify the location and click on Review details
  • Select or unselect specific components and click on Export

Here is how the exported vsconfig file looks like:

Remark: Support for extensions got included in Visual Studio 2022 v17.9. As the feature is quite new, not everything is supported yet.

Extensions can be added manually by specifying them in the extensions section in the vsconfig file:

More information

Customize & save your personal Visual Studio IDE settings - Visual Studio (Windows) | Microsoft Learn

Synchronize settings across multiple computers - Visual Studio (Windows) | Microsoft Learn

Import or export installation configurations | Microsoft Learn

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...