NET features does tend to be ahead of Rider GUI tools for project files / properties is more complete, Rider’s is quite minimal Still have to have VS for a narrow range of scenarios but moving to. Integrated datagrip is a very nice touch that VS simply lacks, though that being said there’s usually a better DB GUI out there On good hardware Rider is much faster, however VS tends to perform better on more limited PCs csproj file editing is better supported in Rider If you’re developing on Linux or Mac or jumping around OS’s, VS simply isn’t viable VS absolutely pales against the JB toolbox as a whole. If you’re a polyglot that has use of the other IntelliJ IDEs, the consistency of experience Rider provides becomes quite valuable.
Rider devs can easily pull off code changes VS devs seriously struggle with using this. The IntelliJ / rider plug-in ecosystem is generally better/richerįind in path in IntelliJ IDEs is a superpower. Rider’s git support is generally loads better and more intuitive than VS
R# is nothing like as good in VS as in Rider, if you want to take advantage of R#, Rider is the way to go I introduced Rider to my company a bit over a year ago and we’ve been using them side by side:
0 kommentar(er)
