publish-vscode-extension
vscode-cpptools
publish-vscode-extension | vscode-cpptools | |
---|---|---|
3 | 63 | |
192 | 5,351 | |
- | 0.5% | |
6.8 | 9.3 | |
about 1 month ago | 7 days ago | |
TypeScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
publish-vscode-extension
-
VS Code or VS Codium - Which should I use?
I have written a number of extensions, and I use the publish-vscode-extension GitHub action to publish my extensions to both marketplaces.
-
GitHub Action You Need to Publish VS Code Extensions
Lastly we will package and publish our extension using the Visual Studio Code Extension Manager and a GitHub Action called HaaLeo/publish-vscode-extension. The advantage of having the packaging and publishing step separated is that we can attach the compiled .vsix file as an artifact to the workflow and offer it as download. Make sure to generate a token (named in the workflow as VSC_MKTP_PAT and OPEN_VSX_TOKEN) to allow GitHub to publish your extension.
-
Write a VS Code extension in JavaScript, not TypeScript ^
I use this github action to automate publishing of an extension to both marketplaces, publication is triggered when the main branch is updated. There a couple of other github actions for
vscode-cpptools
-
Xmake: A modern C/C++ build tool
Now if only MS would fix VSCode[0] :'(. Come on, the feature if more than half a decade old and this point.
0: https://github.com/microsoft/vscode-cpptools/issues/6302
-
🚀 Exciting New Feature Proposal for C++ Developers: "Add Similar Function" in IntelliSense! 🚀
🔗 Link to GitHub Issue: Add Similar Function - https://github.com/microsoft/vscode-cpptools/issues/11477
-
How to enable pretty printers?
According to this: https://github.com/microsoft/vscode-cpptools/issues/3423 it seems to be at least somewhat possible to reuse natvis files from Visual Studio, but I have not tested that. Never really had the need to look at any non-vector container in the debugger.
-
How to Debug C/C++ with Visual Studio Code (From a Microsoft Software Engineer)
Thank you for the feedback! Perf is always an ongoing issue for us but I can say that we’ve recently allocated one of our senior engineers to take on more perf related issues. Something that really helps us out is if you could file reproducible steps that lead to your performance issue. This allows us to address the issues more readily. Please file your issues here: https://github.com/microsoft/vscode-cpptools/issues
-
How to Setup VSCode for C/C++ Programming (From a Microsoft Software Engineer)
Yes, see this github issue for an example: Add Ada to supported languages for debugging · Issue #10475 · microsoft/vscode-cpptools (github.com)
-
Me after trying to use Git with Eclipse
Nope https://github.com/microsoft/vscode-cpptools/issues/16
- [Vscodium] L'extension C / C ++?
- εχει τρεξει κανεις cuda σε visual studio code ;
-
I can't properly use "Run C/C++ file"
and finally, it you're not happy using the extension I provided you, try fo contact the C/C++ Extension repo on GitHub, they'll help you out with your issue. Here's the link: https://github.com/microsoft/vscode-cpptools
-
[Vscode] VSCode me donnant une erreur lorsque j’utilise le débogueur : "launch: program enter name n’existe pas"
Vous devez définir le nom de votre exécutable dans launch.json. Ils expliquent ce qu'il faut faire et comment ici : https://github.com/Microsoft/vscode-cpptools/blob/master/launch.md
What are some alternatives?
tabout - Tab out of quotes, brackets, etc for Visual Studio Code
CodeLLDB - A native debugger extension for VSCode based on LLDB
vscode-git-graph - View a Git Graph of your repository in Visual Studio Code, and easily perform Git actions from the graph.
vscode-clangd - Visual Studio Code extension for clangd
vscode-vsce - VS Code Extension Manager
vscodium - binary releases of VS Code without MS branding/telemetry/licensing
flatpak-vscode - Integrate Flatpak with VSCode
vscode-lldb - A native debugger extension for VSCode based on LLDB [Moved to: https://github.com/vadimcn/codelldb]
publish-extensions - Scripts for publishing VS Code extensions to open-vsx.org
nvim-dap - Debug Adapter Protocol client implementation for Neovim
vscode-extension-samples - Sample code illustrating the VS Code extension API.
Bear - Bear is a tool that generates a compilation database for clang tooling.