| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I6d82544fb98afcba8911cb58ed21cdaad61e7681
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
|
|
|
|
|
|
|
|
|
| |
See the Qt Visual Studio Tools Wiki on how to use the file.
This makes it fairly easy to test the update mechanism or to
deploy the extension in-house.
Change-Id: Ia85fba35b8859d88732e0d86dcf5c929be208d8c
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
Since the VS Gallery expects each VSIX having a different GUID,
we need to have a separate .vsixmanifest file per VS version.
Put the configuration stuff in a dedicated directory, split the
AfterBuild from the actual .csproj and have a .targets file and
.vsixmanifest per Visual Studio version. Update the README file.
Change-Id: I32ffee1c40345812b7f2232987e4e7a5b20c3da6
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
|
|
|
|
|
| |
Change-Id: I3c4cae799b92fb383aebed0505c48c774e86f3ed
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
|
|
|
|
|
| |
Change-Id: I6b929257c3baeb5f347a560184d7efb6e1d0fc58
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
|
|
|
|
|
| |
Change-Id: I76d76c5b538330397f4d7ad75c36038495a1aca6
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
|
|
Change-Id: I68bfb1cb43c1126dc6bb6b12c9c1cba208250f5d
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
|