3 ms·
Hard disagree on the tooling costs. VS Enterprise is $250/month per seat. VS Code is way too limited for most .Net projects. …and that’s if you can even figure
by parkingrift 5y ago
Hard disagree on the tooling costs. VS Enterprise is $250/month per seat. VS Code is way too limited for most .Net projects.
…and that’s if you can even figure out how to manage your VS licensing within the deep abomination that is the MS sign-on and management. Most frustrating experience of my life entire professional life was dealing with O365, Visual Studio, and Azure subscriptions.
- joe_guy 5y ago$250 is several hours of most developers pay. If it saves them any amount of time it's incredibly easy to justify. It's also rare to need what Enterprise has that Professional does not.
- rr808 5y agoRider is $349/year
- runevault 5y agoNote this is the organization price. If you are buying for individual it is $149 or you can get the full suite for $249 (going down $50/year for years 2 and then 3+ stays at $149)
- cerved 5y agoRider is also a good piece of software. VS is garbage
- Smaug123 5y agoHave you tried VS2022, which is basically a complete rewrite? In my limited experience, it's dramatically better than VS2019.
- jpeter 5y agoWhy do you need VS Enterprise? Professional is enough and costs $45 / month
- TowerTall 5y agoCommunity edition is the same version as pro and cost zero.
- hackerfromthefu 5y agoAgreed, Pro/Community covers everything you need.
- deleted 5y ago[deleted]
- 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.