overview for angrysaki

[–] angrysaki 2 points 1 year ago

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.

Is Rider that great? in c/csharp

[–] angrysaki 1 points 1 year ago

The issue I have with the watch window is that I want to have 2 watch windows side by side, so i can compare to separate variables side by side. For Rider I find i have to use the locals window as one of my watches which is often really cumbersome.

Honestly, what I really want is an IDE tool to give me some sort of "diff" of objects while debugging, but the 2 separate watch windows is the best I've found.

Is Rider that great? in c/csharp

[–] angrysaki 3 points 1 year ago (3 children)

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.

10

Is Rider that great? (self.csharp)

submitted 1 year ago by angrysaki to c/csharp

10 comments fedilink

I'm partly just posting this to get some more content going here...

...but I've been using Rider for the past year or so, and I'm not sure I can say it's better than Visual Studio. I find anytime it comes up it's all praise for Rider (including the debugger, which i find to be crap)

The Pros:

--IdeaVim is better than VsVim

--Feels a bit snappier

--The find in files pops up in a dialog box with "display as you type"

Cons:

--I really don't like the debugger layout. It's not customizable at all and I find I'm going back and forth between tabs all the time

--The debugger also doesn't have a second watch window, which blows my mind. (I often want to compare the state of 2 variables side by side, which is a huge pain in Rider)

--It has a bad bug where sometimes it won't recompile my changes, so I have adopted the workflow of always deliberately building before debugging, which is annoying.

--Doesn't work with WinForms

I just always see comments about how much better Rider is. It has some advantages, but it has some massive flaws IMO too. I'm not sure what I'm going to use going forward. Right now I'm developing in rider and debugging in VS.