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

Labels:

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         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more