3 ms·
>VS Code is way too limited for most .Net projects. I've been forcing myself to use VS Code for my last few C# projects and it's actually quite usable once you
by HideousKojima 5y ago
>VS Code is way too limited for most .Net projects.
I've been forcing myself to use VS Code for my last few C# projects and it's actually quite usable once you get used to the quirks and limitations. The biggest issues:
1) You really need to understand the dotnet CLI tools or you're going to be in for a world of hurt
2) Omnisharp craps the bed way too often. Restarting it from the command palette fixes 99% of the issues though.
3) You need to know the ins and outs of launch.json and task.json in VS Code if you want to do anything more complicated than build and attach. Full VS is much easier to work with here.
- ripley12 5y ago> Omnisharp craps the bed way too often. FWIW I've had a much better experience with OmniSharp since they shipped a version running on .NET 6 (opt-in with the "omnisharp.useModernNet" setting). YMMV but I need to restart it much less now. https://www.strathweb.com/2022/01/hello-omnisharp-on-net-6-0/ https://www.strathweb.com/2022/01/hello-omnisharp-on-net-6-0...
- HideousKojima 5y agoYeah I'm running the .NET 6 version of Omnisharp and it's definitely a major improvement, but it's still got a ways to go.
- CharlieDigital 5y agoI did the same thing and hard forced myself to code in VS Code and now I'm fully comfortable working in VS Code on macOS. The main stumbling blocks are really around debugging setup. A lot of stuff that VS IDE proper sets up for you automatically you have to manually wire up in VS Code.