"We've noticed that extension 'ReSharper Ultimate' is slowing Visual Studio" message

In case you get this

2017-07-11_1339.png

and this

2017-07-11_1339_001.png

or that

2017-08-17_1118.png

We have no idea how MS team counts that number of seconds in VS performance monitor. Sometimes it complains about its Error List  https://developercommunity.visualstudio.com/content/problem/16041/vs-2017-rc-weve-noticed-that-a-tool-window-error-l.html or something else.

If you notice a real performance problem apart from that message, first of all, please try following this guide https://www.jetbrains.com/help/resharper/Speeding_Up_ReSharper.html

If those steps did not help and you still experience the performance problem, please follow https://resharper-support.jetbrains.com/hc/en-us/articles/207243205 article to send us a perf snapshot.

9 comments

You don't deny the fact that the IDE freezes when it boots up, though, right?

Just an observation.

 

It gets old having to manually close the major yellow banner across the top, but indeed, performance isn't truly affected. 

I would follow your guide for performance, but it explicitly means I must disable features that I would rather not disable.
Guess it's something to deal with like many things in life. I refuse to go back to Visual Studio without resharper. So if I must toil with a yellow banner, so be it..

Edited by ensemblebd
3

on the right - "Never show this again"

 

There, I fixed it

-1

I'm afraid that in my experience R# creates significant slowdown during loading of large projects and even worse during debugging, especially when compared to VAX, I really hope this can be improved upon.

1

I also get this warning from Visual Studio (so that people googling it can find this page).

Extension 'JetBrains ReSharper Ultimate 2017.3.3 11.0' likely caused 7 seconds of unresponsiveness. Disabling it may improve your experience.

4

I also get this message every single time I open Visual Studio 2017. And sure, I can have it stop showing the message. (By the way, mine says it cause 11 seconds of unresponsiveness.) But it is annoying that it takes so long to start up!

And like ensemblebd, I have reviewed the Performance Guide that Resharper keeps recommending I use to improve performance, but then why use Resharper at all? Most of the stuff it recommends to disable is stuff I want to use! If I disabled all of the preferences affecting performance that it recommended, then I might as well not even start up Resharper and just use the built-in VS enhancements that they have made. I am about ready to completely disable R# for a day and see how performance is without it!

2

The performance is so terrible, I have found integrated roslyn VS2017 extensions to pretty much replace all of resharper, at least for the actions and functions my team uses. We all immediately noticed VS2017 is super responsive and usable again. So far that is 10 of us moving off of reshaper and cancelling subscriptions. I will say took me about 2 weeks to get used to the differences, but with the latest release of VS2017 and the reshaper keyboard mapping we are fully joy.

 

#ByeResharper #NeverLookBack

Edited by D Turco
3

Same thing here, but my only problem with the banner is the visual disturbance. Is there a way to suppress it specifically for ReSharper? I don't want to disable the warning for all addons.

0

Same here. This is getting old!

Running windows 10 on bootcamp on MacBook Pro Touchbar (custom build with upgraded CPU)

0

Guys, guys, those are rookie numbers! Its telling me it is causing 60+ seconds of unresponsiveness!!!

It's a big solution (70+ projects) but to me that seems unreasonable

My set up is Windows 10 Enterprise 64 bit, Intel Core i7-8650U @ 1.90GHz 2.11GHz, 32GB RAM

I've turned off all the VS features that were reccomended by Resharper in the performance options section apart from codelense, as I find this very useful and turned off Solution wide analysis in Resharper too. However it is still clunky as hell. Its my first few weeks using Resharper and I want to give it an honest try, but I can't work with it atm and if I'm honest all of the features my colleagues tell me about to try and convince already exist in vs 2017 so as of the moment I'm not sold

0

Please sign in to leave a comment.

Have more questions?

Submit a request