clang-format vs plugin support for Visual Studio 2017
authorHans Wennborg <hans@hanshq.net>
Fri, 31 Mar 2017 12:50:42 +0000 (12:50 +0000)
committerHans Wennborg <hans@hanshq.net>
Fri, 31 Mar 2017 12:50:42 +0000 (12:50 +0000)
With the release of Visual Studio 2017, we need to at the very least
claim support for it in the current manifest file. With the changes
introducted in this patch we can install the extension again, but a
warning message will be shown stating that it's not supported
(https://twitter.com/parsley72/status/846558416751411200).

To get the rid of the warning more work is necessary, as VS 2017 changed
some things about extensions, see more here:
https://docs.microsoft.com/en-us/visualstudio/extensibility/how-to-migrate-extensibility-projects-to-visual-studio-2017.
While working on those changes, it has been suggested in the
mail list that this first patch is integrated in the meantime.

Patch by Hugo Puhlmann!

Differential Revision: https://reviews.llvm.org/D31522

llvm-svn: 299210

clang/tools/clang-format-vs/source.extension.vsixmanifest.in

index 496fa40063b7d035c995b512f0c05f8b1a33a874..55440e1426b399fb8b3c13cbddfbd4457d0a9d88 100644 (file)
@@ -22,6 +22,9 @@
       <VisualStudio Version="14.0">\r
         <Edition>Pro</Edition>\r
       </VisualStudio>\r
+      <VisualStudio Version="15.0">\r
+        <Edition>Pro</Edition>\r
+      </VisualStudio>\r
     </SupportedProducts>\r
     <SupportedFrameworkRuntimeEdition MinVersion="4.0" MaxVersion="4.0" />\r
   </Identifier>\r