[ripperdoc]

I can echo this, while doing its job most of the time, Omnisharp has been one of the least stable parts of my VS Code C# experience (the least stable as usual being anything relating to Unity ;) ).

Issues like runaway compiler threads, slow response times, OmniSharp frequently losing the mono-path and requires restart (this is some config issue and interaction with Unity, but could have been handled automatically).

It's sensible to improve the C# experience on VS Code, but not saying the way MS is doing it here is the best way.

[jve]

Ah, no wonder I felt unproductive with C# on VSCode. I couldn't wrap my head around that it is now how you should write C# code with such bad intellisense n stuff.

[throwuxiytayq]

A few years ago I spent a couple of months using C# w/ vscode. The experience was indeed harrowing.

Omnisharp would take forever to start up (always downloading a new Omnisharp binary on every restart for some reason?!), type checking was unresponsive to the point of being unusable, and the whole thing would freeze and stop working entirely every once in a while, requiring me to reload the IDE. I tried various versions of Omnisharp (stable/beta) across many C# projects and several vscode deployments on multiple machines and never got it to work well. I eventually decided Omnisharp would never improve and abandoned vscode because of how uniformly bad it was for C#.