Recently, I\u2019ve updated over 30 of my extensions to support Visual Studio 2019 (16.0). To make sure they work, I got my hands on a very early internal build of VS 2019 to test with (working on the Visual Studio team has its benefits). This upgrade process is one of the easiest I\u2019ve ever experienced.<\/p>\n
I wanted to share my steps with you to show just how easy it is so you\u2019ll know what to do once Visual Studio 2019 is released.<\/p>\n
We need to make a couple of updates to the .vsixmanifest file. First, we must update the supported VS version range.<\/p>\n
Here\u2019s a version that support every major and minor versions of Visual Studio 14.0 (2015) and 15.0 (2017) all the way up to but not including version 16.0.<\/p>\n
<Installation InstalledByMsi=\"false\"> \r\n <InstallationTarget Id=\"Microsoft.VisualStudio.Pro\" Version=\"[14.0,16.0)\" \/> \r\n<\/Installation><\/pre>\nSimply change the upper bound of the version range from 16.0 to 17.0, like so:<\/p>\n
<Installation InstalledByMsi=\"false\">\r\n <InstallationTarget Id=\"Microsoft.VisualStudio.Pro\" Version=\"[14.0,17.0)\" \/>\r\n<\/Installation><\/pre>\n<Prerequisite><\/h4>\n
Next, update the version ranges in the <Prerequisite> elements. Here\u2019s what it looked like before:<\/p>\n
<Prerequisites> \r\n <Prerequisite Id=\"Microsoft.VisualStudio.Component.CoreEditor\" Version=\"[15.0,16.0)\" DisplayName=\"Visual Studio core editor\" \/> \r\n<\/Prerequisites><\/pre>\nWe must update the version ranges to have the same upper bound as before, but in this case we can make the upper bound open ended, like so:<\/p>\n
<Prerequisites> \r\n <Prerequisite Id=\"Microsoft.VisualStudio.Component.CoreEditor\" Version=\"[15.0,)\" DisplayName=\"Visual Studio core editor\" \/> \r\n<\/Prerequisites><\/pre>\nThis means that the Prerequisite needs version 15.0 or newer.<\/p>\n
If you have a dependency on Microsoft.VisualStudio.MPF then delete it. This dependency is a legacy one that hasn’t been needed since before Visual Studio 2010. It looks something like this:<\/p>\n
<Dependencies>\r\n <Dependency Id=\"Microsoft.VisualStudio.MPF.14.0\" DisplayName=\"Visual Studio MPF\" d:Source=\"Installed\" Version=\"[14.0]\" \/>\r\n<\/Dependencies><\/pre>\nSee the updated .vsixmanifest files for Markdown Editor<\/a>, Bundler & Minifier<\/a>, and Image Optimizer<\/a>.<\/p>\n
Next Steps<\/h2>\n
Nothing. That\u2019s it. You\u2019re done.<\/p>\n
Well, there is one thing that may affect your extension. Extensions that autoload a package has to do so in the background as stated in the blog post, Improving the responsiveness of critical scenarios by updating auto load behavior for extensions<\/a>. You can also check out this walkthrough on how to update your extension to use the AsyncPackage\u00a0<\/a>if you haven\u2019t already.<\/p>\n
What about the references to Microsoft.VisualStudio.Shell<\/em> and other such assemblies?<\/strong> As always with new version of Visual Studio, they are automatically being redirected to the 16.0 equivalent and there is backwards compatibility to ensure it will Just WorkTM<\/sup>.\u00a0 And in my experience with the upgrade is that they in fact do just work.<\/p>\n
I\u2019m going to head back to adding VS 2019 support to the rest of my extensions. I\u2019ve got about 40 left to go.<\/p>\n","protected":false},"excerpt":{"rendered":"
Recently, I\u2019ve updated over 30 of my extensions to support Visual Studio 2019 (16.0). To make sure they work, I got my hands on a very early internal build of VS 2019 to test with (working on the Visual Studio team has its benefits). This upgrade process is one of the easiest I\u2019ve ever experienced. […]<\/p>\n","protected":false},"author":642,"featured_media":222750,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[155],"tags":[294,475],"class_list":["post-19115","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-visual-studio","tag-extensions","tag-visual-studio-2019"],"acf":[],"blog_post_summary":"
Recently, I\u2019ve updated over 30 of my extensions to support Visual Studio 2019 (16.0). To make sure they work, I got my hands on a very early internal build of VS 2019 to test with (working on the Visual Studio team has its benefits). This upgrade process is one of the easiest I\u2019ve ever experienced. […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/19115","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\/642"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=19115"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/19115\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/222750"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=19115"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=19115"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=19115"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}