[thrower123]

I fail to see what the point of trying to use VS Code for .NET development would be. I suppose if you like tying one hand behind your back and making things more difficult for yourself for some reason. Or maybe you like cobbling together a rickety pile of plugins.

If cost is a concern, there's Rider or even MonoDevelop.

[manigandham]

OmniSharp is the official C# plugin and all you need for .NET projects, and it's usually installed by default. VS Code starts faster, runs lighter, and provides 80% of the functionality of VS for most major products, and it's getting better every release. I find it more productive than VS for typical web projects.

[james_s_tayler]

For proper .NET projects I've used both VS Code, VS and Rider.

VS Code doesn't come close.

I use VS Code when doing front end stuff with Vue/TypeScript and I love it for that, but .NET Core was painful on VS Code compared to Rider.

[fgonzag]

Vscode is lightweight, I don't really refactor all that often, and it's code search function is first class (so is it's vim emulation), and it has a terminal.

Since dotnet core includes a CLI executable, I interact with the project through the CLI. I manually edit the config files. I could run the stack from a netbook if I wanted to.

[jackfoxy]

I work mainly in multi-project F# solutions. VS Code Ionide plug-in seems pretty solid for single project F#, but every time I've tried to use it for multi-project I run into some sort of situation that sends me back to Visual Studio.

VS has had it's own F# problems. The latest Preview edition is pretty solid, with one annoying bug. Almost every time I open my big multi-project solution I need to rebuild to get Intellisense to eliminate the red squigglies, and then close VS and re-open. It's a known issue. Hope MS fixes it soon.