This was only true for the first releases, they have been integrating common code from VS and this is one of the reasons why VS moved away from COM plugins into a .NET ones.
https://gist.github.com/mtone/aded2ff636cb6dd9d428cf5800f344...
Funnily, I have no clue how to setup a build script in Rider, did that in VS (Rider do run it).
For some reason I can’t change the position of the debugger when running and aspnetcore app and make it go back so I always have to re-run whatever request I happen to be debugging. Does that happen to you?
It also seems like ReSharper had more tips and tricks going on when compared to Rider, but I can’t imagine that would be true.
Any tips, tricks, or pitfalls to avoid making the switch from VS to Rider?
Rider was what I thought I'd give a go, with the idea that if it was really terrible I'd fire up a VM with Windows and VS.
As someone who's used Visual Studio since VS 2002, and ReSharper since (probably) 2006 - moving to Rider was pretty much run and go.
There's a few minor differences, but the only one that bugged me was the regional formatting options for the debugger. I still havn't figured out how to set it to use ISO8601 or something like it for formatting dates/times, and instead it picks something based on my OS configuration.
And all of our .NET Core services on MacOS, with all my unix-y tooling.
There is “VS for Mac”, but it’s not really VS. It’s Xamarin Studio rebranded.
Rider works excellent on my Linux box at home as well, where the alternatives are MonoDevelop and Omnisharp + text editor.