SSD Upgradeįirst of all, upgrade to SSD drives if you’re still using those old-fashioned spinning-disk drives. Not off to a great start.Tweaking the environment to speed up Visual StudioĮvery developer’s dream is to work on an environment capable of responding the commands, compiling and debugging in alignment with the developer’s speed of thought.Īlthough such computers and development tools do not exist on the market yet, there’re a few tricks that could boost Visual Studio performance and responsiveness, reduce the time spent for builds, and increase overall productivity and efficiency. So while the unresponsiveness notification is an indicator, it may not be 100% accurate.Īnd yet it disappears when ReSharper is uninstalled as does the latency. ReSharper can be blamed for the unresponsiveness notification – even though it is not the real culprit. "Well-oiled" engine with massive performance issues that you yourselves described as super complex with tons of legacy code in the first blog post. Although not off to a good start:Ī better question would be the following: is it worth replacing a well-oiled engine just to work around the limited 32-bit working set? But if all this is is a series of excuses and blaming others, I'm just done with ReSharper. I'll keep an eye on this, and might even re-sub if they actually do something. Disabling it may improve your experience.įinally got Jetbrains to take it seriously after how many years? Or is it that customers (like me) are jumping ship to solutions that use Roslyn natively and perform much better (Roslynator, etc)? Every ReSharper patch for the last two years all I've looked for is performance improvements and yet nope. Seems like Microsoft's new-ish notification shaming them:Įxtension ‘JetBrains ReSharper Ultimate’ likely caused 9 seconds of unresponsiveness.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |