4 ms·

I started using Rider recently. It's faster yes, but seems to be a bit more memory hungry out of the gate than VS+Resharper. There is one HUGE thing I miss ho

I started using Rider recently. It's faster yes, but seems to be a bit more memory hungry out of the gate than VS+Resharper. There is one HUGE thing I miss however - the Package Manager console. There's still a few things I have to do in there and thus have to switch back to VS.

m_fayer 7y ago
Definitely more memory hungry. But I see it as a good deal. I feed it all the memory it wants, it gives me stability, xplat, and an embarrassment of riches as far as features and conveniences. It's earned that memory.
eyegor 7y ago
You can achieve this through nuget.exe from your hidden /.nuget directory iirc.
- to11mtm 7y ago
  Not everything. I can't do the equivalent of update-package -reinstall A forced package restore doesn't quite do the same thing. (I'm really glad Rider has that feature though!) Add-BindingRedirect (would be extra handy since Rider doesn't handle redirects at all [1]) [1] https://youtrack.jetbrains.com/issue/RIDER-5482 https://youtrack.jetbrains.com/issue/RIDER-5482
tigershark 7y ago
VS is 32 bit, so instead of getting more memory when it needs it slows to a crawl and eventually crashes. I think that the early versions of VS are a bloodbath. VS 2019 just crawled with a small solution just because there were mixed C# and F# projects. I should remember to upgrade always after 2 or 3 minor revisions instead of being a guinea pig for MS. On the other hand some time ago I got a bug in rider where the F# code worked perfectly in VS but didn’t work at all in rider and until today I have rider highlighting some errors in perfectly valid c# code but the build is successful while for resharper that code is fine. And the biggest current pain that I have is that I cannot debug ny tests in VS but they work perfectly in rider. So for now I’m sticking to both of them until rider irons up some small wrinkles.
- peteri 7y ago
  Tests not running might be X86/X64 issue. Certainly nUnit will find the tests but not run them until you change the default architecture (Resharper will run them happily in VS).
tablloyd 7y ago
Theres a nuget & terminal tab across the bottom bar which combined offer the same functionality as the nuget package manager console.
- to11mtm 7y ago
  See my other reply. There's not 100% replication, there are some things you just plain can't do outside VS. =(

m_fayer 7y ago

Definitely more memory hungry. But I see it as a good deal. I feed it all the memory it wants, it gives me stability, xplat, and an embarrassment of riches as far as features and conveniences. It's earned that memory.

eyegor 7y ago

You can achieve this through nuget.exe from your hidden /.nuget directory iirc.

to11mtm 7y ago
Not everything. I can't do the equivalent of update-package -reinstall A forced package restore doesn't quite do the same thing. (I'm really glad Rider has that feature though!) Add-BindingRedirect (would be extra handy since Rider doesn't handle redirects at all [1]) [1] https://youtrack.jetbrains.com/issue/RIDER-5482 https://youtrack.jetbrains.com/issue/RIDER-5482

tigershark 7y ago

VS is 32 bit, so instead of getting more memory when it needs it slows to a crawl and eventually crashes. I think that the early versions of VS are a bloodbath. VS 2019 just crawled with a small solution just because there were mixed C# and F# projects. I should remember to upgrade always after 2 or 3 minor revisions instead of being a guinea pig for MS. On the other hand some time ago I got a bug in rider where the F# code worked perfectly in VS but didn’t work at all in rider and until today I have rider highlighting some errors in perfectly valid c# code but the build is successful while for resharper that code is fine. And the biggest current pain that I have is that I cannot debug ny tests in VS but they work perfectly in rider. So for now I’m sticking to both of them until rider irons up some small wrinkles.

peteri 7y ago
Tests not running might be X86/X64 issue. Certainly nUnit will find the tests but not run them until you change the default architecture (Resharper will run them happily in VS).

tablloyd 7y ago

Theres a nuget & terminal tab across the bottom bar which combined offer the same functionality as the nuget package manager console.

to11mtm 7y ago
See my other reply. There's not 100% replication, there are some things you just plain can't do outside VS. =(