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

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

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.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...