Official support for VS 2017 and later #33
Comments
rpaquay
added a commit
that referenced
this issue
Aug 4, 2017
* Move to VSIX manifest v3 to avoid warning when installing on VS 2017. * Sources * http://www.visualstudioextensibility.com/2017/01/10/its-time-to-change-the-vsix-manifest-of-your-extension-to-v3-for-visual-studio-2017-compatibility/ * https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/docs/extensibility/faq-2017.md#can-i-build-a-vsix-v3-with-visual-studio-2015
rpaquay
added a commit
that referenced
this issue
Aug 4, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See issue #28: Even though VsChromium works with VS 2017, there is a scary warning when installing the extension:
The following extensions are not compatible with Visual Studio 15. Installation may cause Visual Studio to be unstableSee http://www.visualstudioextensibility.com/2017/01/10/its-time-to-change-the-vsix-manifest-of-your-extension-to-v3-for-visual-studio-2017-compatibility/ for instructions on how to upgrade VsChromium to be compatible wit the new manifest format.
Note: To support the new manifest format, the VsChromium solution must first be upgraded to VS 2015 (it is currently built with VS 2013).
The text was updated successfully, but these errors were encountered: