Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to Export/Import Toolbars in Visual Studio
    primarykey
    data
    text
    <p>I export my settings in Visual Studio and if I ever move to a new machine or have problems, I use those backed up settings to restore Visual Studio to the way I like it. It also allows me to maintain a consistent development environment between the various machines that I use.</p> <p>This works great for keybindings, syntax highlighting, user tools, pretty much everything except for the <strong>toolbar locations</strong> and <strong>customizations</strong>. Whenever I move to a new machine and restore the settings, the toolbars are not affected. I have spent a fair amount of time setting up toolbars with my macros, external tools, etc and cut'n'pasted icons in for them. I hate losing all that work.</p> <p>Does anybody know how to back up and restore the toolbars' locations and customizations? If it is not a feature of Visual Studio, is there an addin that will do the job?</p> <p><strong>Edit</strong></p> <p>As mentioned below, the <em>Menu and Command Bar Customizations</em> in <em>Import and Export Settings</em> is supposed to do this, but when I re-import my previous settings, I get </p> <blockquote> <p>Error 1: Menu and Command Bar Customizations: The version of command bar settings being imported is not supported. All the command bar settings have been ignored.</p> </blockquote> <p>The settings I am trying to re-import were exported earlier this month with the same version of Visual Studio. The only difference is that I am now running 64 bit as opposed to x86. I didn't think that would make a difference though since the settings files are XML.</p> <p>Any ideas?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload