Cursor cannot use C# to develop extension packs：C# Dev Kit, has anyone encountered it? How was it resolved?
3 Likes
Me too, C/C++ extension also meet same wrong.
I tried to roll back the version of the expansion pack to previous versions and found that it could be used.
3 Likes
Microsoft is starting to limit third parties because of the competition
1 Like
No, these restrictions have always been there. Microsoft is just starting to enforce it more judiciously. Cursor ignoring the restriction isn’t Microsoft’s fault.
Microsoft can be a ■■■■■■■■■■■■■ company, but put blame where it belongs.
2 Likes
Using previous version of the extension is just a temporary solution. Cursor needs to actively work on solving this problem.
3 Likes
v1.16.6 seems to work for now.
1 Like
I understand there’s an ongoing “IDE war” between the company behind Cursor and Microsoft. While I see the reasoning from a business perspective, as a developer I’m extremely frustrated that I can no longer use Cursor for development (at least not with my current .NET projects). To be honest, Copilot doesn’t even come close to Cursor in terms of quality.
My question is: Are you (the company behind Cursor) planning to address the issues Microsoft is imposing — even if they are technically within their rights — that effectively prevent your users from working with Cursor? I know .NET developers might currently be a minority among cursor’s user base, but there’s clearly potential for a growing .NET audience who would love to adopt Cursor in the future.
To me, it feels like having the keys to a Lamborghini but being forced to lock them away, while you’re stuck driving an old beat-up Toyota because someone is prohibiting you from driving the “better” car on the roads you use. As I’ve written above, I get it, but I don’t like it.