It’s Time to Update Your VS 2017 Extension Manifest

This post has been republished via RSS; it originally appeared at: Channel 9.

Carlos Quintero, Mr. Extension and Friend of the Blog, posted a great tip on what Visual Studio Extension creators should do to ensure their extension is truly ready for VS 2017...

It’s time to change the VSIX manifest of your extension to v3 for Visual Studio 2017 compatibility

 

"I still see, even as today Jan 10, people asking why you get this error when trying to install your extension on Visual Studio 2017 RC:

“The following extensions are not compatible with Visual Studio 15. Installation may cause Visual Studio to be unstable”:

image

or this other one when you try to upload the extension to the Visual Studio Gallery:

“This extension targets Visual Studio 2017 but was not build with an up-to-date VSSDK. Please make sure to update your references and try uploading again. Note: you’ll also need to add Prerequisites to your extension.vsixmanifest.”:

In both cases, the answer is the same: you have just updated the extension.vsixmanifest of your Visual Studio 2015 extension to add 15.0 (for Visual Studio 2017):

...

But that is not enough to add compatibility for Visual Studio 2017. Even worse, some people wonder if you can live ignoring those warnings.

The short answer to make an extension compatible with Visual Studio 2017 is the following:

... [Click through to see the details]