Registering and initializing user tool windowsĪ VSPackage project template that is installed together with Visual Studio SDK allows you to create a sample tool window in the extension project which this template generates. Integration of a tool window into the IDE is supported by VSPackage and Add-In extensions (although the methods for it are different) it requires the specification of the window's initial settings and its registration in the system registry. A toolwindow can also be associated with a certain UI context (as the so called dynamic window), and such window will be automatically displayed when the user enters this context. But still, is it possible to crate Multi-Instance toolwindows in the IDE, which are the windows that can exist in several instances at once. Therefore, pressing the 'close' button on a tool window does actually hide it, and when this window is invoked for the second time, it becomes visible again, thus preserving any data that it contained before being 'closed'. In most cases IDE creates and utilizes just a single instance for each one of its toolwindows, and this instance will be preserved until IDE itself needs to shut down. PVS-Studio Output Window itself can be opened from Visual Studio main menu (PVS-Studio -> Show PVS-Studio Output Window), but it also will be invoked automatically each time the analysis starts. All other of its tool windows can be opened from this main window, as, for example, a search window for the grid. Usually tool windows' contents are not associated with any files and do not contain any editors, as separate document windows are reserved for such tasks.įor instance, PVS-Studio extension package integrates several tool windows into the IDE, with Output Window being the primary one. Solution Explorer and Error List are the examples of tool windows. Tool windows are child windows of Visual Studio MDI (Multiple Document Interface) interface and they are responsible for presenting various pieces of information to the user. You can read the new version of this article here. Discussed are the issues of window registration and initialization in VSPackage and Add-In plug-in modules, hosting of user components and handling of window's events and states. This article covers the extension of Visual Studio IDE through integration of a custom user toolwindow into the environment.
0 kommentar(er)
