summaryrefslogtreecommitdiffstats
path: root/clang/tools/clang-format-vs/source.extension.vsixmanifest.in
Commit message (Collapse)AuthorAgeFilesLines
* clang-format extension: Widen the supported versions rangeHans Wennborg2019-06-131-1/+1
| | | | | | | | So that it covers also the latest VS 2019 version. By Antonio Maiorano! llvm-svn: 363230
* clang-format vs plugin: Visual Studio 2019 supportHans Wennborg2019-04-151-1/+1
| | | | llvm-svn: 358402
* clang-format-vs: Update the VSIX ID.Hans Wennborg2017-09-121-1/+1
| | | | | | | | We're moving the extension to a new account on the VS Marketplace, and apparently it's not possible to re-upload an extension with an existing ID on a new account. llvm-svn: 313060
* Warning-free clang-format plugin install for VS 15.0Hans Wennborg2017-04-131-36/+16
| | | | | | | | | | | | | | | | | | | | With the new release of VS, it's required that all plugins migrate to the new VSIX manifest format. The new format is backwards compatible with all versions newer that Visual Studio 2012, so this migration effectively drops support for older versions of the IDE. It's also required that these new extensions are built with Visual Studio 2017, so unfortunately it was necessary to migrate the project and solution. Also removed COM references to EnvDTE and Microsoft.VisualStudio.TextManager.Interop from the csproj, as they seem to both be unnecessary and would trigger build warnings because of changes to GAC. Patch by Hugo Puhlmann! Differential Revision: https://reviews.llvm.org/D31740 llvm-svn: 300225
* clang-format vs plugin support for Visual Studio 2017Hans Wennborg2017-03-311-0/+3
| | | | | | | | | | | | | | | | | | | | 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-format vs plugin: claim support for VS 14 CTP tooHans Wennborg2014-08-011-0/+3
| | | | llvm-svn: 214461
* clang-format vs plugin: include the licenseHans Wennborg2014-07-291-0/+2
| | | | | | | | | The vsix installer will show the license when it starts, and it would print an annoying message when there was none. While we're here, add a MoreInfoUrl. llvm-svn: 214237
* clang-format vs plugin: set version number from cmake (PR20307)Hans Wennborg2014-07-211-0/+31
Previously it was hard-coded to 1.0, which meant the installer would not install the plugin over previous versions. This commit makes us use LLVM's major.minor.patch version from cmake, or whatever CLANG_FORMAT_VS_VERSION is set to when configuring the build. It's pretty dirty to update a configuration file in the source directory from the cmake build like this. However, the plugin build is already dirty in this regard since it builds in the source dir when visual studio, and then copies out the resulting vsix. llvm-svn: 213584
OpenPOWER on IntegriCloud