<\/p>\n
Using extensions in Visual Studio 2022<\/h3>\n
For many of you, having your ideal, 64-bit Visual Studio 2022 experience is not complete without the extensions that are essential to your development environment.\u00a0 If you\u2019re an existing extension author, you\u2019ll need to successfully migrate your extension to be VS 2022-compatible using the VS 2022 extension migration guidance<\/a>.\u00a0 Many popular extensions such as CodeRush<\/a>, VSVim<\/a>, Productivity Power Tools<\/a>, and most Mads Kristensen extensions<\/a> are available now, and there will be more to come as we approach VS 2022\u2019s official release.<\/p>\n <\/p>\n We are now offering extensions to the Language Server Protocol functionalities which let you leverage capabilities specific to Visual Studio.\u00a0 Servers can use these additional contracts to provide additional functionalities such as diagnostics info and project contexts when communicating with a Visual Studio instance.<\/p>\n To get started, check out the LSP extension documentation<\/a> and download the related NuGet package<\/a>.<\/p>\n <\/p>\n One of the biggest hurdles to writing a VS extension is that they can be hard to write, especially when you\u2019re just starting out.\u00a0 We\u2019ve heard from authors and aspiring authors that this is due to numerous factors, including hard-to-discover, dated APIs, inconsistent, inaccurate documentation, and lack of best extensibility practices.<\/p>\n To tackle this issue, we have created the Visual Studio Community Toolkit.\u00a0 This toolkit is a community-driven set of project templates, API wrappers, and productivity tools that provide a simpler, streamlined experience for writing extensions in Visual Studio.<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n The recommended way to get started is to head on over to the VSIX Cookbook<\/a> and follow the guide. There\u2019s lots of easy-to-follow tutorials, videos, and code samples to get you going.\u00a0 The best part about the Community Toolkit is the community! If there are additional scenarios you\u2019d like to see added to the toolkit, you can contribute to and provide feedback for the Community Toolkit and other open-source projects by checking out the VSIX Community org on GitHub<\/a>.<\/p>\n <\/p>\n Extensions crashing VS.\u00a0 Lack of secure extensions.\u00a0 Inconsistent documentation.\u00a0 Having to restart VS when installing extensions.\u00a0 These are some of the most common frustrations extension users and writers have expressed in the past few years.\u00a0 Compared to the current model, the new extensibility model loads extensions out-of-process.\u00a0 This allows for more reliable extensions that won\u2019t cause Visual Studio to hang or crash.\u00a0 Like the Community Toolkit, this new model will make extensions easier to write with more cohesive APIs and documentation.\u00a0 Also, extensions written with the out-of-proc model let you install them without restarting VS. Last but not least, these extensions can be placed in low-trust environments, protecting your dev machine.<\/p>\n Phase 1 allows you to write and F5-debug out-of-proc, command-focused extensions working with open documents such as single-file linters and formatters using the new model’s editor API.\u00a0 Writing linter extensions such as spell checkers provides your users with diagnostic info in the VS editor via squiggles and error list entries.\u00a0 Writing a formatter extension lets your users easily “prettify” or format their code.\u00a0 Publishing out-of-proc extensions to the VS Marketplace is still to come!<\/p>\n <\/p>\n No!\u00a0 Continue using the current model for any VS 2022 extensions that will be distributed to users and\/or published in the VS Marketplace.<\/p>\n The new extensibility model is a long, ongoing project. As a result, it won’t be available at full feature parity and general consumption by the end of VS 2022\u2019s release cycle. Whether you\u2019re new to writing extensions or you\u2019re an extension-writing pro, we encourage you to try writing an extension using the new model<\/a> and share your feedback under Issues in the VSExtensibility repository<\/a>!<\/p>\n <\/p>\n Overwhelmed by all the new extensibility additions and not sure which one(s) you should use?\u00a0 Ask yourself the following questions:<\/p>\n Follow the migration guidance<\/a> to make sure your audience can use their essential extensions in VS 2022.<\/p>\n Check out the new expansion options for LSP<\/a> when communicating between servers and VS instances.<\/p>\n Install and use the Visual Studio Community Toolkit<\/a>!<\/p>\n Try out phase 1 of the out-of-proc extensibility model!<\/a><\/p>\n Bookmark the VSExtensibility repo (aka.ms\/vsextensibilityupdates)<\/a>, your hub for all upcoming extensibility-related announcements.\u00a0 As we embark on this journey toward an improved extensibility experience, don\u2019t forget to share your feedback under Issues<\/a>!<\/p>\n","protected":false},"excerpt":{"rendered":" Visual Studio 2022 seeks to greatly improve your overall development experience, and we’re moving forward with that journey in improving VS extension writing and usage today!\u00a0 We have several exciting extensibility updates that are either available now or on the horizon, so let’s check them out!<\/p>\n","protected":false},"author":651,"featured_media":234300,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1388,155],"tags":[294,12,6815],"class_list":["post-234400","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-extensibility","category-visual-studio","tag-extensions","tag-visual-studio","tag-visual-studio-2022"],"acf":[],"blog_post_summary":" Visual Studio 2022 seeks to greatly improve your overall development experience, and we’re moving forward with that journey in improving VS extension writing and usage today!\u00a0 We have several exciting extensibility updates that are either available now or on the horizon, so let’s check them out!<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/234400","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/651"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=234400"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/234400\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/234300"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=234400"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=234400"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=234400"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"Image](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/09\/vs2022-marketplace.png\")
<\/a>Expand Language Server Protocol (LSP)<\/h3>\n
Easier extension writing with the Visual Studio Community Toolkit<\/h3>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/09\/toolkit-templates.png\")
<\/a>![\"Image](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/09\/toolkit-insert-guid.png\")
<\/a>![\"Image](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/09\/toolkit-icon-intellisense.png\"){kind=icon}
<\/a>![\"Image](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/09\/toolkit-intellisense-command-placement.png\")
<\/a>How do I get started with the Community Toolkit?<\/em><\/h4>\n
Write securer, more reliable extensions with the new, Out-of-Proc Extensibility Model<\/h3>\n
What can I do with the new extensibility model in Phase 1?<\/em><\/h4>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2021\/09\/linter-example.png\")
<\/a>Is the current extensibility model being deprecated?<\/em><\/h4>\n
How do I get started with the out-of-proc model?<\/em><\/h4>\n
There are so many updates!\u00a0 Where and when should I use each one?<\/h3>\n
How do I make sure my extension is compatible with Visual Studio 2022?<\/em><\/h4>\n
How can I expand LSP functionality in my projects?<\/em><\/h4>\n
Extensions are difficult and tedious to write! What tools can help make the experience easier?<\/em><\/h4>\n
I\u2019m feeling experimental and want to share my feedback on the future of extension writing.\u00a0 What should I do?<\/em><\/h4>\n
How do I keep track of all these ongoing extensibility developments?\u00a0<\/em><\/h4>\n