Tool Windows in the Registry


The new home for Visual Studio documentation is Visual Studio 2017 Documentation on

The latest version of this topic can be found at Tool Windows in the Registry.

VSPackages that provide tool windows must register with Visual Studio as tool window providers. Tool windows created by using the Visual Studio Package template do this by default. Tool window providers have system registry keys that specify visibility attributes, such as default tool window size and location, the GUID of the window that serves as the tool window pane, and docking style.

During development, managed tool window providers register tool windows by adding attributes to the source code, and then running the RegPkg.exe utility on the resulting assembly. For more information, see Registering a Tool Window.

Unmanaged tool window providers must register with Visual Studio in the ToolWindows section of the system registry. The following .reg file fragment shows how a dynamic tool window might be registered:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\<version number>\ToolWindows\{f0e1e9a1-9860-484d-ad5d-367d79aabf55}]  
"Float"="250, 250, 410, 430"  

In the first key in the example above, version number is the version of Visual Studio, such as 7.1 or 8.0, the subkey {f0e1e9a1-9860-484d-ad5d-367d79aabf55} is the GUID of the tool window pane (DynamicWindowPane), and the default value {01069cdd-95ce-4620-ac21-ddff6c57f012} is the GUID of the VSPackage providing the tool window. For an explanation of the Float and DontForceCreate subkeys, see Tool Window Display Configuration.

The second optional key, ToolWindows\Visibility, specifies the GUIDs of commands that require the tool window to be made visible. In this case, there are no commands specified. For more information, see Tool Window Display Configuration.

VSPackage Essentials