Monday , July 22 2019
Home / Uncategorized / How to update extensions to support Visual Studio 2019

How to update extensions to support Visual Studio 2019



Recently, I updated over 30 of my extensions to support Visual Studio 2019 (16.0).

To make sure that they work, I get my hands on a very early internal build of VS 2019 to test (working with the Visual Studio team has its advantages). I learned that the upgrade process is probably the simplest I've ever seen.

I wanted to share this experience with you to show how easy it is. So you'll know what to do once you get a copy of Visual Studio 2019.

Updates to .vsixmanifest

We need to make a couple of updates to the .vsixmanifest file. First of all, we need to update the VS version range supported.

Here is a version that supports all major and minor versions of Visual Studio 14.0 (2015) and 15.0 (2017) up to version 16.0.

 

Just change the upper limit of the version range from 16.0 to 17.0, like this:

 

Next, update the version intervals to elements. Here's how it looked before:

 

We need to update the version ranges to have the same upper limit as before, but in this case we can finish the upper limit open, like this:

 

This means that the Prerequisite requires version 15.0 or later.

View updated .vsixmanifest files for Markdown Editor, Bundler & Minifier and Image Optimizer.

What & # 39; other?

Anything. That's all. Are you done.

Well, there's one thing that could influence your extension. Extensions that automatically upload a package must do so in the background as indicated in this blog post. Take a look at this great tutorial on how to make this change if you have not already done so since it was supported by Visual Studio 2015.

What about references to Microsoft.VisualStudio.Shell and other assemblies of this kind? As always with the new version of Visual Studio, they are automatically redirected to the equivalent 16.0 and compatibility with previous versions guarantees that it will work properly.TM. And in my experience with the update is that they actually only work.

I plan to go back to adding VS 2019 support to the rest of my extensions. I still have 40 to do.


Source link

Leave a Reply

Your email address will not be published.