5 ms·

I find VS2022 to be anything but slow now that it’s 64bit. Having said that, without ReSharper I find VS to be a terrible experience (I’ve been using R# for 15

I find VS2022 to be anything but slow now that it’s 64bit. Having said that, without ReSharper I find VS to be a terrible experience (I’ve been using R# for 15 years.) Rider is also a viable alternative.

tester756 5y ago
Have you tried Roslynator instead of R#?
hughrr 5y ago
I have a project here that won’t even open with Resharper on in VS2022. It just hangs and wedges the CPU at 100%, then my shitty laptop overheats and hibernates. Then I get pissed off and go for a walk and wonder why the hell I ever invested so much time in this.
- GiorgioG 5y ago
  Laptops have always been a compromise between portability, battery life, thermals, and performance. In my opinion, Visual Studio was never meant to run well on a laptop.
  - hughrr 5y ago
    I’ve got a desktop it sucks just as hard on. That just makes my feet warm instead.
    - GiorgioG 5y ago
      I've worked on some legacy solutions that did indeed suck to open (100+ projects in a single solution), but none that would fail to load completely.
ejb999 5y ago
>>without ReSharper I find VS to be a terrible experience Resharper was always one of my favorite must have utilities to use for C# development in VS - but I have had the opposite experience as you, it became so slow and so bloated I had to give it up - often spiking my CPU to 100% and making the entire solution unusable - until I uninstalled it. Never could figure out why, but maybe resharper has gotten better since then?
- phillipcarter 5y ago
  > Never could figure out why, but maybe resharper has gotten better since then? R# runs in-process and has its own project system, language service, UI elements, etc. That's simply a lot of stuff to do in the same process that also has the VS project system, language service(s), UI elements, etc. running. Both have added tons of features over the years, so over time it just slows down. The R# team is working to run it out of process, but it's an enormous amount of work. I suspect that VS 2022 (64-bit) will help with this compared to previous versions though.

tester756 5y ago

Have you tried Roslynator instead of R#?

hughrr 5y ago

I have a project here that won’t even open with Resharper on in VS2022. It just hangs and wedges the CPU at 100%, then my shitty laptop overheats and hibernates. Then I get pissed off and go for a walk and wonder why the hell I ever invested so much time in this.

GiorgioG 5y ago
Laptops have always been a compromise between portability, battery life, thermals, and performance. In my opinion, Visual Studio was never meant to run well on a laptop.
- hughrr 5y ago
  I’ve got a desktop it sucks just as hard on. That just makes my feet warm instead.
  - GiorgioG 5y ago
    I've worked on some legacy solutions that did indeed suck to open (100+ projects in a single solution), but none that would fail to load completely.

ejb999 5y ago

>>without ReSharper I find VS to be a terrible experience Resharper was always one of my favorite must have utilities to use for C# development in VS - but I have had the opposite experience as you, it became so slow and so bloated I had to give it up - often spiking my CPU to 100% and making the entire solution unusable - until I uninstalled it. Never could figure out why, but maybe resharper has gotten better since then?

phillipcarter 5y ago
> Never could figure out why, but maybe resharper has gotten better since then? R# runs in-process and has its own project system, language service, UI elements, etc. That's simply a lot of stuff to do in the same process that also has the VS project system, language service(s), UI elements, etc. running. Both have added tons of features over the years, so over time it just slows down. The R# team is working to run it out of process, but it's an enormous amount of work. I suspect that VS 2022 (64-bit) will help with this compared to previous versions though.