{"id":238911,"date":"2022-08-10T09:00:08","date_gmt":"2022-08-10T16:00:08","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/visualstudio\/?p=238911"},"modified":"2022-08-10T00:00:24","modified_gmt":"2022-08-10T07:00:24","slug":"visualstudio-extensibility","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/visualstudio-extensibility\/","title":{"rendered":"VisualStudio.Extensibility: A New Way to Write Extensions"},"content":{"rendered":"

Last year, we announced the first phase of a new extensibility model for Visual Studio<\/a>.\u00a0 This new model will make extensions easier to write and more reliable along with additional benefits such as being able to install these extensions without restarting the IDE.\u00a0 Now, we\u2019re excited to announce the second phase of the new extensibility model, now titled VisualStudio.Extensibility!<\/p>\n

 <\/p>\n

What’s new for phase 2 of VisualStudio.Extensibility?<\/h3>\n

Phase 1 enabled editor APIs that let you create linter and formatter extensions.\u00a0 The following VisualStudio.Extensibility APIs allow you to write richer, non-language-based productivity extensions.<\/p>\n

Remote UI Framework<\/h5>\n

Adding UI can be an important part of creating an extension. \u00a0Now you can create UI-based extensions with the addition of the WPF-based Remote UI framework<\/a>.\u00a0 Unlike the in-proc UI framework in the previous model, Remote UI is out-of-proc and fully asynchronous, relying on a Model-View-ViewModel design pattern, XAML, data binding, and commands.<\/p>\n

Tool Windows<\/h5>\n

Using the new Remote UI framework, extensions can now provide custom tool windows. Tool windows can be registered with a default placement (such as floating in the document well, relative to other VS tool windows) and auto-creation (allowing the window layout to recreate and show the tool window when needed). Additional support is included for using context rules to dynamically show and hide a tool window. also new extensibility APIs for finding, showing, and hiding these tool windows. All the new tool window behaviors are set up to be asynchronous including getting the tool window\u2019s properties and content.<\/p>\n

\"Tool<\/a>
Sample code for creating a tool window<\/figcaption><\/figure><\/p>\n

 <\/p>\n

\"Tool<\/a>
Tool window example<\/figcaption><\/figure><\/p>\n

 <\/p>\n

New Editor API Additions<\/h5>\n

The VisualStudio.Extensibility editor scenarios are expanding!\u00a0 Now you can do the following:<\/p>\n