open-vsx.org VS vscode-cpptools

You can follow https://github.com/rust-lang/rust-analyzer/issues/11080 for news. Publishing to OpenVSX has been implemented on the RA side for 27 days, but it fails because of a server-side problem. https://github.com/EclipseFdn/open-vsx.org/pull/1094 (which took 24 days to merge) was supposed to fix it, but it might have been rolled back and I don't think it worked for RA anyway.

looks the warnning would dismiss after this issue approved https://github.com/EclipseFdn/open-vsx.org/issues/476

I just wanted to highlight that Open VSX is not an issue, and is not inferior to the Visual Studio Marketplace (as some people are led to believe when they find missing extensions), but rather an awesome project providing a vendor-neutral FLOSS extension registry. The real "issue" to be solved is getting more users and extension authors aboard the train, to fill Open VSX with more extensions and one day make it on-par with the Visual Studio Marketplace. Just the other week, GitHub (a Microsoft owned company!) decided to become a verified publisher on Open VSX, so I have high hopes that we'll get there.

🔗 Link to GitHub Issue: Add Similar Function - https://github.com/microsoft/vscode-cpptools/issues/11477

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.

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

Yes, see this github issue for an example: Add Ada to supported languages for debugging · Issue #10475 · microsoft/vscode-cpptools (github.com)

Nope https://github.com/microsoft/vscode-cpptools/issues/16

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

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