As of ~6 hours ago, the "C# Dev Kit" and "C/C++" extensions no longer work in Cursor.<p>Error message: "extension may be used only with Microsoft Visual Studio Code and other Microsoft affiliates' products."<p>Why I think this matters:<p>Yes, Microsoft's license does explicitly state that its extensions (and the entire VSCode plugin registry, really) are for use in VSCode only. So technically, this move is within their rights.<p>Cursor has likely been using a workaround to access MS's extension catalog. But now it looks like Microsoft is enforcing those restrictions — at least for C, C++ and C# Dev Kit.<p>What worries me is whether this is just a one-off... or if Microsoft is testing the waters and might start blocking other key extensions (TypeScript, Python, etc.) or even ban Cursor entirely from the registry.<p>PS:<p>It’s kinda wild that Cursor — a well-funded company directly competing with MS (re: Copilot) — is relying on Microsoft’s infrastructure in a way that’s clearly against the TOS. They’re basically operating with an axe hanging over their head.<p>PPS: Windsurf next?<p>---<p>UPD: screenshot can be viewed at https://i.imgur.com/WTyQMFk.png<p>UPD2: reddit threads<p>https://www.reddit.com/r/cursor/comments/1jrl981/microsoft_has_released_their_own_cursor/<p>https://www.reddit.com/r/dotnet/comments/1jtxsxd/as_of_6_hours_ago_c_dev_kit_is_not_working_in/<p>https://www.reddit.com/r/cursor/comments/1jr1fbq/cc_vscode_extension_is_getting_blocked_on_cursor/
Here’s where we are with what Microsoft is doing:<p><pre><code> Embrace (Open Source, Github, Linux) [x]
Extend (AI, VSCode, WSL) [x]
Extinguish <——————- (We are here) (Close to ‘Free’, Blocking extensions)
</code></pre>
When Microsoft sees a fast growing threat to one of their flagship AI products (Github Copilot) thanks to Cursor, desperate measures become activated.<p>Microsoft will then attempt to race Cursor to zero to try to destroy them to become the best tool for close to free.
Does anyone know how is the filtering done? Is it just the user agent or something similar? I suspect a proxy, or some small patch should be possible to use in the meantime...<p>Edit: vscodium seems to have workarounds <a href="https://github.com/OliverKeefe/vscode-extensions-in-vscodium">https://github.com/OliverKeefe/vscode-extensions-in-vscodium</a>
Why are you even using DevKit instead of standard base extension or, moreover, its fork which uses NetCoreDbg, used by VSCodium and other proper forks?