Hacker News Reader

Comment by runevault | Hacker News Reader

Been thinking about switching to Rider (already had the personal license for Jetbrains from wanting CLion for Rust) and figured .NET 6 would be a good time to try making the switch. With how blah VS has been for a while hopefully I'll like the Rider experience better (for both c# and f#)

Edit: Though I saw something this morning when I tried to load an f# project I made in VS refused to load even though the new ones generated with Rider are fine...

View on HN

I switched from VS to Rider a few years back - it's great, and I'm so glad I made the move!

Rider feels so much faster than VS, and is rock solid - these were my 2 main reasons for switching from VS.

I've been using Rider for a couple of months now for Xamarin projects, as Visual Studio was for unknown reasons unbearable slow on my iMac - it totally destroyed my workflow and productivity.

Rider is not perfect, but in many ways miles above Visual Studio.

As Rider doesn't have any Forms editor build-in (AFAIK), I am slowly switching most of my views to fully code, so I don't need to rely on Visual Studio's visual layout editors anymore.

It does but only on Windows and for C# projects:

https://www.jetbrains.com/help/rider/Working_with_Windows_Fo...

Compare the generated project file between the two.

I noticed for a time that some projects created in rider had a different project type than those created in VS which caused some issues at my company. Was a simple change to the proj file though.

I'd love to give Rider a try but I need SQL Projects. VSCode and DataStudio both have support for it now so I'm hoping they figure out how to bring it into Rider as well.

I switched to Rider a few years ago. I really like it and I find its Vim emulation a lot lot better than what you can get for Visual Studio. Its F# support is ok, but I'd say VSCode+Ionide is better. But Rider isn't bad for F# still, and it has other tools it brings.

+1 for Rider. It’s one of the 2 .NET IDEs I know that don’t suck terribly (the other being the proprietary version of VSCode).

> proprietary version of VSCode

Do you mean Visual Studio? They don't share anything AFAIK

The binary VScode you install is different than an open source build. Microsoft doesn't want OS builds using the same package registery and I assume various tooling iirc

Very interesting. I wasn't aware of that.

Reply on news.ycombinator.com