HAharporoeder·Nov 29, 2022Submission
A roadmap update on the VS Code C# extension
2 points · Open discussiondotnet
vscode-csharp
TypeScript2016–2024
dotnet / vscode-csharp
vscode-csharp
Official C# support for Visual Studio Code
27Distinct people
33Mentions
0Explicit recommenders
3.1KGitHub stars
What to know before exploring
What it is
Official C# support for Visual Studio Code
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- dotnet/core · linked in 2 of the same discussions
- dotnet/roslyn · linked in 2 of the same discussions
- microsoft/vscode · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year33 dated mentions
Observed mentions: 2016-02-24 22:54:21 UTC to 2024-10-22 18:34:10 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 16 | 3 | 13 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 6 | 2 | 4 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 6 | 0 | 6 |
What Hacker News says
16 sourcesFor me its been the questionable stewardship of vscode (https://github.com/omnisharp/omnisharp-vscode/issues/5276) driving me away from vscode and the Emacs from Scratch videos from the System Crafters youtube channel driving me towards Emacs. When I was looking for alternatives I stumbled on those videos and they blew me away.
Also Emacs 28/29 has been way more welcoming and easy to get started with than when I first tried 8 or so years ago.
In Emacs 29 is nighTechnically the restrictions already exist, just as a part of the development experience.
- .NET Hot Reload is only implemented on Windows. It requires support in the .NET runtime, which is technically possible to implement, but the team has not gotten around to implementing it for years. This doesn't have to do with the issue around MS removing the "dotnet watch" command, it's for the "Edit and Continue" feature in IDEs.[1][2]
- MS was considering deprecating Omnisharp, the open-source language server that implements C# support for VS Code, and replacing it with a closed-source version. Since the announcement, commits to omnisharp-vscode have dropped off significantly. The lack of Omnisharp would mean there would be no real open-source C# development environment for Linux anymore, since MonoDevelop was abandoned a few years ago.[3]
[1] h
Read the rest
I wouldn't lose a second to C# or any MS platform unless required for employment reasons.
https://github.com/OmniSharp/omnisharp-vscode/issues/5276
In The Case for C# and .NET>> All things considered, it's well past time to stop being so harsh on Redmond. Stop judging Microsoft on what it did a decade ago and judge it by what it's doing today.
You mean like closed sourcing previously open source VS Code extensions?
They recently announced that they are closed sourcing the C# VS Code extension:
"Once the “LSP Tools Host” is complete, this will become the default experience for the C# for VS Code extension. Existing users will be able to choose between the open-source OmniSharp powered system that exists today, or the new “'LSP Tools Host” which will provide access to additional experiences. The “LSP Tools Host” will not be open-sourced, but we plan to communicate with the community along the way to help guide our future plans."[1]
The same thing was done with PyLance which was "extended" from PyRight.[2]
Why wo
Read the rest
uld they do this?
Because VS Code can't get good enough to compete with Visual Studio. If it did, they would lose revenue by not selling enough copies of Visual Studio.
It's the same Microsoft, they've just had to adapt since they lost a lot of the power they had in the past.
[1] https://github.com/omnisharp/omnisharp-vscode/issues/5276
[2] https://devblogs.microsoft.com/python/announcing-pylance-fas...
This is a great example of it happening in the .NET world:
https://github.com/OmniSharp/omnisharp-vscode/issues/5276
In Microsoft begins “Extinguish” phase of dealing with Open SourceWhat a shame it doesn’t list the latest scandal by MS.
https://github.com/OmniSharp/omnisharp-vscode/issues/5276
In Microsoft Donated Money to Gnome: Remember How They Attacked Open Source BeforeHow is Microsoft reducing your ability? No functionality got behind a paywall. On contrary, the VS Code plugin will actually get much better because of this effort - you can read the authors of OmniSharp clearly stating this[0], links are in the comments above. Microsoft spends a lot of money to bring you free experiences. Then it has the business on top of that where it offers better experience. Nothing different to what JetBrains does in this regard. Except that this fuels how you are able to fund the free experience in the first place.
[0] https://github.com/omnisharp/omnisharp-vscode/issues/5276#is...
In Despite best efforts .NET is still not an open platformThese comments from an OmniSharp contributor are particularly enlightening:
https://github.com/omnisharp/omnisharp-vscode/issues/5276#is...
https://github.com/omnisharp/omnisharp-vscode/issues/5276#is...
In Despite best efforts .NET is still not an open platformAh come on! It's more complicated than that.
Most of the heavy lifting in OmniSharp is done by Roslyn [0]. Roslyn is the open source C# compiler and code analysis library maintained by MS. You cannot overstate how much effort has gone into Roslyn, and how much money MS has invested to make it work. OmniSharp is essentially a wrapper[1] around Roslyn (before Roslyn it was Mono), and while the OmniSharp team did a nice job developing a nice intellisense UX around it all, it is not like MS is taking it all away from them. Incidentally, it is almost certain that new intellisense plugin by MS will also be built on top of Roslyn.
[0] https://github.com/dotnet/roslyn
[1] https://github.com/OmniSharp/omnisharp-vscode#the-c-extensio...
In Despite best efforts .NET is still not an open platformThe actual announcement is here:
https://github.com/omnisharp/omnisharp-vscode/issues/5276
It's not quite as dramatic as the OP is making it out to be.
In Despite best efforts .NET is still not an open platformMicrosoft discloses plans to turn parts of VS Code C# extension to closed source
112 points · Open discussionA roadmap update on the VS Code C# extension
13 points · Open discussionShowing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.