When making a new small .net core api, I've actually found VS to be a little overkill compared to just VSCode. And as such, i believe the .net dev experience may be less of a factor for windows OS dominance as we move towards a unified .net with .NET 5.
Agreed. I work at a .NET shop as a front end dev and, while I don't write a ton of C#, I find running VS to be overkill for 90% of anything I do. The only upside I see of VS is if you REALLY need ReSharper, in which case you should just use Rider. VSCode is fast, has great Intellisense plugins and feels overall more polished than VS now days.
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
When making a new small .net core api, I've actually found VS to be a little overkill compared to just VSCode. And as such, i believe the .net dev experience may be less of a factor for windows OS dominance as we move towards a unified .net with .NET 5.
Agreed. I work at a .NET shop as a front end dev and, while I don't write a ton of C#, I find running VS to be overkill for 90% of anything I do. The only upside I see of VS is if you REALLY need ReSharper, in which case you should just use Rider. VSCode is fast, has great Intellisense plugins and feels overall more polished than VS now days.