getcursor
Has the VSCode C/C++ Extension been blocked?
While coding just now I got this msg:
The C/C++ extension may be used only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services to develop and test your applications.
Is this new? Will VSCode extensions no longer be usable on cursor?
Looks like the latest version of the extension has blocked it from working, but a temporary fix that worked for me was to downgrade it and disable auto update.
On the extension page, the drop-down next to "uninstall" has a "install specific version". Install version 1.23.6
UPDATE: Microsoft has released their own Cursor AI competitor, thus they've blocked VSCode forks like Cursor from using MS extensions
This was inevitable, especially given how they chose to build and deliver Cursor. Hopefully they enjoyed the ride while it lasted.
The extensions block is a classic, old school, msft business move. They were always going to eat Cursors lunch. Tbh I'm surprised it took this long.
Looks like the license on some of the underlying tools for the C++ extension has prohibited this for at least 5 years. Must just now be enforcing it. https://github.com/microsoft/vscode-cpptools/blob/main/RuntimeLicenses/cpptools-LICENSE.txt
Yeah, this sounds like it was inevitable for Cursor. Interested in hearing what the plan is.
Worth mentioning that Microsoft's own language extensions have always stated you can't use it outside of Visual Studio Code (and that Code forks don't count), it's definitely not a new issue, just that it's something they've decided to enforce now for the C++ extension.
https://github.com/microsoft/vscode-cpptools/blob/main/RuntimeLicenses/cpptools-LICENSE.txt
Here's an older 2018 issue where they've clearly said no with using the C# extension on Code forks.
https://github.com/dotnet/vscode-csharp/issues/2491#issuecomment-418811364
It can be worked around by diff the old and new version code then bypass it manually.
Looks like the latest version of the extension has blocked it from working, but a temporary fix that worked for me was to downgrade it and disable auto update.
On the extension page, the drop-down next to "uninstall" has a "install specific version". Install version 1.23.6
thanks for solution! @cbartzis-lancaero which the latest version works?
If this is not resolved and at least a decent C++ extension is provided by Cursor, I will not pay any premium to Cursor.
I downloaded the 1.24.4 vsix from the releases page, and installed it in cursor with "Extensions: Install from VSIX..." option, then restarted extensions. Seems to be working fine.
I'd much rather have a supported current version though, so interested in updates on this.
I don't have a horse in this race but I suppose this will result in a large shift to Open VSX alternatives (eg clangd and clang-tidy)
I don't have a horse in this race but I suppose this will result in a large shift to Open VSX alternatives (eg clangd and clang-tidy)
I should learn how to use clangd…
If this is not resolved and at least a decent C++ extension is provided by Cursor, I will not pay any premium to Cursor.
I think it's unfair to blame cursor when the real problem is Microsoft's monopoly.
AMACM: awful microsoft anti-competition mechanism. I think it's unfair to blame cursor when the real problem is Microsoft's monopoly.
I think it's totally fair to blame Cursor. Microsoft's C/C++ tools are big business for them. That should have been a given considering that the license agreement literally said this:
The C/C++ extension may be used only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services to develop and test your applications.
Cursor actively and purposefully chose to ignore Microsoft's EULA on this when there's both free/OSS and paid competitors that they could have integrated. Things such as GCC/G++, Clang/LLVM, the Embarcadero Compiler, and others that I can't think of off the top of my head. They also apparently chose to actively and purposefully include the full VS Code Extensions Hub, another thing that's prohibited by Microsoft's licensing regarding VS Code forks (hence why most forks point to Open VSX).
This is ALL on Cursor. It's their fault full stop.
I'm so annoyed, I've been tinkering for a long time and thought I did something wrong!!!
In fact, branches based on the open source code of VSCode are not allowed to use Microsoft's plugin store, which was written in the agreement from the very beginning. Cursor has been violating this agreement through reverse proxy, and at least in this matter, Microsoft is not at fault.
If we cannot distinguish right from wrong, but instead think everything Microsoft does is evil, then we are no different from the "evil corporations" we despise.
In fact, branches based on the open source code of VSCode are not allowed to use Microsoft's plugin store, which was written in the agreement from the very beginning. Cursor has been violating this agreement through reverse proxy, and at least in this matter, Microsoft is not at fault.事实上，基于 VSCode 开源代码的分支是不允许使用 Microsoft 的插件商店的，该插件商店从一开始就写在协议中。 Cursor 一直通过反向代理违反本协议，至少在这件事上，Microsoft 没有过错。
If we cannot distinguish right from wrong, but instead think everything Microsoft does is evil, then we are no different from the "evil corporations" we despise.如果我们无法区分是非，而是认为 Microsoft 所做的一切都是邪恶的，那么我们与我们鄙视的“邪恶公司”没有什么不同。
This is exactly where its evil lies: the whole world knows: release water to raise fish, and then harvest you!
Seems like there're 2 camps emerging: Cursor is bad, they didn't read the terms AND Microsoft is evil, they are pressing on the competition :)
Regarding the licensing terms, to me it seems that the users who install and use extensions are obliged to follow the associated terms (such as only use it with MS supplied IDEs in case of CPP extension). I don't see why it is Cursor's team fault that users (a) don't read manuals (b) don't read the legal terms (c) don't follow them to the letter - who could have guessed :) Should Cursor team actively block the installation through UI (and spend effort closing all the loopholes, such as directly installing from .vsix files) - I don't think so...
In any way I fully support Cursor team, they did a great job of building a great product with is ergonomically superior to GH CoPilot had many features introduced way before other AI coding assistant had them. A small team was able to build such a nice product, without cutting corners that could be impossible. Hope this issues is eventually sorted out and Cursor users can proceed using their favourite VSCode extension with the lowest friction possible.
Funny how they don't mention that in the changelog. Typical Microsoft, ninja rug-pulling stuff.
