this post was submitted on 19 Jun 2023
10 points (100.0% liked)
C Sharp
1532 readers
2 users here now
A community about the C# programming language
Getting started
Useful resources
- C# documentation
- C# Language Reference
- C# Programming Guide
- C# Coding Conventions
- .NET Framework Reference Source Code
IDEs and code editors
- Visual Studio (Windows/Mac)
- Rider (Windows/Mac/Linux)
- Visual Studio Code (Windows/Mac/Linux)
Tools
Rules
- Rule 1: Follow Lemmy rules
- Rule 2: Be excellent to each other, no hostility towards users for any reason
- Rule 3: No spam of tools/companies/advertisements
Related communities
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think the latest versions of Visual Studio have gotten a bit better regarding performance. I initially switched because of performance issues with a particular solution (which is now fixed). I still find it slower than Rider though.
Regarding the debugger, I do wonder if I'm misusing the Rider debugger, because I've seen lots of comments saying that it's way better than the VS one.
Visual Studio is quite these days snappy (maybe not quite as fast as Rider, but not much worse) but ReSharper makes it way slower.
Which latest version of VS are you referring to? I only switched to Rider a year ago so I was already accustomed to VS 2022 which introduced 64bit extensions and I was still having issue with poor performance.
I will say that VS has a much more versatile UI. Rider sucks at multi-monitor support. VS has always supported docking tool windows together on another screen but Rider just can't do that. The devs recently introduced being able to have a second editor window on a separate screen with docked tool windows so closed the issue on their tracker but it's such a clumsy implementation compared to VS.
I'm on the latest version of the preview (17.7). I think most of the performance enhancements were in the past 6 months, or even less. If you do a search for "visual studio 17.x performance" for x =4 to 6, you should get some devblogs posts about various performance improvements (some drastic).
My guess is that the VS team is prioritizing performance where they were previously putting out fires due to the switch to 64 bit.
I'm on triple monitors and I agree with the lacking multi monitor support.