.NET Integrated Development Environments (IDE) Resources
Discussions and Reports to expand your knowledge on .NET Integrated Development Environments (IDE)
Resource pages are designed to give you a cross-section of information we have on specific categories. You'll find discussions from users like you and reports from industry data.
.NET Integrated Development Environments (IDE) Discussions
The slowest part of starting a new .NET project is often the setup and ramp-up, not the code. So, for the .NET developers and reviewers here: what .NET IDE platforms are best for teams that need rapid implementation and quick adoption without a long onboarding process? A few worth weighing, and what each is best known for on fast starts:
- Visual Studio: best known for being the default most .NET developers already know, so an existing team needs almost no training, and its project templates get a standard app running in minutes. The catch is that the install is large, and it is Windows-only now, so it is not the quick option for a Mac or Linux team.
- JetBrains Rider: best known for a fast, smart editor that works the same on Windows, macOS, and Linux, with a bundled runtime so there is little to configure, and it is free for non-commercial use. The catch is that if your team comes from Visual Studio, the different layout takes a little getting used to.
- Visual Studio Code with the C# Dev Kit: best known for the lightest, fastest setup of the three, a small download that opens in seconds, and it is Microsoft's own cross-platform pick for .NET. The catch is that it’s really an editor with extensions, so heavy .NET work can need more manual setup, and on G2 it sits in the code editor category rather than this one.
Worth saying: the category's older names, MonoDevelop and Codeanywhere, are no longer maintained or available, so they are not real options today.
For teams who onboarded recently, which of these got you from install to first working build the fastest?
VS Code wins install-to-first-build on the clock, but for a team that's the wrong race. First build on one machine isn't the milestone, identical builds on every machine is, and that's where Rider's bundled runtime quietly earns its keep. Visual Studio is only the fast option when the team already knows it, which, to be fair, is most .NET teams.
Visual Studio would get my vote for the fastest first working build if the team is already on Windows and familiar with .NET. The project templates and familiar workflow remove most of the onboarding. For a mixed Windows, Mac, and Linux team, I’d lean toward Rider so everyone can adopt the same environment.
In my experience Rider's identical setup across Windows, macOS, and Linux matters more for a mixed team than shaving a few minutes off any single person's first build, since everyone ending up on the same environment saves time down the line too.
What is Visual Studio used for?
I have written a lot of reviews and all of them are all getting trejeted and I want to know why.