I have DotUltimate and use VSCode to program C# all day every day. It's getting there. Works really well for straight coding. The debugger performance has gotten way, way better and works really well with Asp.Net and tests.
My two biggest beefs right now are the lack of external source code fetching which makes inspecting all the Asp.Net extension magic hard, and then the test explorer experience kinda sucks compared to Rider. It's slow, doesn't watch, switches to the terminal output every time you run a test, and for some reason only only shows output if the test fails. Not a tight feedback loop.
It's getting better though even if it feels like they barely have any resources on it. Still no release notes on updates and every now and then the pre-release versions of C# Base/Devkit break something.
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 give you sense of the state of play right now.
tldr; watch this space; if you're already heavily invested vscode, give it a whirl... but, if you're using a mostly-c# code base, you probably won't want to have it as your primary editor right now.
Last time I tried, about a year ago, it was a mess of multiple pop ups telling me to download things and console windows popping up with progress bars etc. Really confusing. DE at best, not IDE
My two biggest beefs right now are the lack of external source code fetching which makes inspecting all the Asp.Net extension magic hard, and then the test explorer experience kinda sucks compared to Rider. It's slow, doesn't watch, switches to the terminal output every time you run a test, and for some reason only only shows output if the test fails. Not a tight feedback loop.
It's getting better though even if it feels like they barely have any resources on it. Still no release notes on updates and every now and then the pre-release versions of C# Base/Devkit break something.