vscode-dotnettools

Some of Microsoft's extensions are licensed such that they may only be used with their own products (i.e. the official VS Code they offer for download, etc.). This already affects Cursor for example: https://github.com/microsoft/vscode-dotnettools/issues/1909

Exactly. From: [0] >> I know it works as intended. Just curios why Microsoft decided to enforce this all of a sudden. Because they can. Also... >> Did GitHub Copilot just give up on playing fair with Cursor, admitting it's winning? The game wasn't 'fair' to begin with and it was rigged for Microsoft to win anyway. (Cursor being based on VS Code). If you're competing against Microsoft, expect them to race you to zero for years (extinguish) at close to no cost for them. It is all for Cursor to lose if they continue as they are and competitors like Microsoft catch up (and they will do so very quickly whilst lowering prices). [0] https://github.com/microsoft/vscode-dotnettools/issues/1909#...

Indeed. "DID YOU JUST BAN CURSOR?" https://github.com/microsoft/vscode-dotnettools/issues/1909 > The error seems very clear to me. Dev Kit is licensed only for use with VS Code, Cursor is not VS Code, ergo it is not licensed to use it. > > Not to mention that only VS Code can use the official plugin registry in the first place. Everything working as intended.

What are you talking about? This is well documented. https://github.com/microsoft/vscode/issues/30065 https://github.com/microsoft/vscode/issues/48810 https://github.com/dotnet/vscode-csharp/issues/1609 https://github.com/dotnet/vscode-csharp/issues/299 https://github.com/microsoft/vscode-dotnettools/issues/573 https://github.com/dotnet/vscode-csharp/issues/5276#issuecom... https://isdotnetopen.com/ A Rider license costs $419 per year per seat and Jetbrains has a poor quality record by today's standards, and if you are a serious developer that has to use one of their products, you'll find yourself at the mercy of numerous YouTrack tickets that have been open for years. They have a habit of shipping integrations that are only partially working, and then calling it a day (or the better part of a decade). By the way, Rider may have been chea

Compared to what? To visual studio? It's bad. To rider? It's bad. To the level of support in vscode, for example, for typescript? It's bad. To using a potato? It's pretty good! To using a plain-text editor? Pretty sweet! To using the old omnisharp plugin? haha... is there anything that isn't better than that? Seriously though, if you want an honest answer: It's not that bad... but, its frustrating after using a different editor. They're now investing in making it better (1), and it is better than it was a year ago. Expect to see more improvements in this space. ..but like, yeah. Right now, it kind of still sucks if you're working in C# full time, compared to the serious alternatives. You can see common themes on the issue tracker (2), if you want a less anecdotal response, or perhaps dig through a couple of the juicy threads (3), that giv