VS' debugger allows you to manipulate code while debugging it, with some limitations e.g when you're writing COM code, but generally the craziest thing I did was putting breakpoint after SQL bad call, editing SQL string, at function exit adding call to itself with passing the same args, going into the same function and catching the same breakpoint while executing new SQL and then removing that function call and letting program continue.

it allows you to evaluate expressions at fly

it allows you to back in time (move e.g 2 LoC above)

it allows you to use the Immediate window to debug and evaluate expressions, execute statements, and print variable values. The Immediate window evaluates expressions by building and using the currently selected project.

I still haven’t tried it, but apparently rider is even better than VS. Especially for unity developers as it gives informations from the code as well as the Game asset files.

I used VS for something like 15 years, before switching to Rider few years back - Rider's debugger is now even better than VS's, IMO.

For example, I always found "edit and continue" really flakey in VS - it was really slow, sometimes using it resulted in a long hang or an outright crash, and quite often the IDE wouldn't even give me the option to use it. Rider is rock-solid by comparison - I'd say VS (with ReSharper) and Rider are roughly at feature parity, but Rider kicks VS's arse on stability and performance.

Another thing I'd add is that all of Microsoft's UserVoice-type feedback sites are an absolute joke - you might as well be piping your ideas into `/dev/null`. I feel like JetBrains actually listens much more to what developers are asking for.

Huge fan of Rider, and actually JetBrains the company too.