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. Well, there is one thing that may affect your extension. vsixmanifest files for Markdown Editor, Bundler & Minifier, and Image Optimizer. This dependency is a legacy one that hasn’t been needed since before Visual Studio 2010. If you have a dependency on then delete it. This means that the Prerequisite needs version 15.0 or newer. We 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: Next, update the version ranges in the elements. Simply change the upper bound of the version range from 16.0 to 17.0, like so: Here’s 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. First, we must update the supported VS version range. We need to make a couple of updates to the. I wanted to share my steps with you to show just how easy it is so you’ll know what to do once Visual Studio 2019 is released. This upgrade process is one of the easiest I’ve ever experienced. 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).
Recently, I’ve updated over 30 of my extensions to support Visual Studio 2019 (16.0).
0 kommentar(er)
