Download older version resharper

With that knowledge, we expect that having a bit process will significantly reduce memory pressure in the IDE, which will automatically lead to Visual Studio with ReSharper being more performant for memory-critical operations.

There is still room for optimization. We will keep working on ReSharper out-of-process. With Rider, we saw that running memory- and CPU-intensive operations in different processes, and wiring these processes with an asynchronous API, leads to a better development experience.

For example, the ReSharper process could perform solution-wide analysis without interrupting the Visual Studio process where you are working in the editor. Also, not all our customers immediately upgrade their Visual Studio version, so having ReSharper out-of-process will benefit them as well. Less memory contention means less garbage collections, which means less pauses to the UI and other tasks.

For CPU-intensive tasks, we will have to wait for the first preview version of Visual Studio to see what will happen. As you will see in the ReSharper out-of-process issue in our tracker, there are some open items pending. With every release, we work on ReSharper performance improvements.

In the latest A lot of progress has been made. We can successfully load a full solution, a partial solution from a. A number of tool windows are working, and we can extend existing tool windows in Visual Studio from the background process. For example, ReSharper OOP can extend the Properties tool window with some ReSharper-specific properties, you can edit them in Visual Studio, and these changes flow back to the background process. Many actions that do not rely on the text editor, are ready to go!

Solution-wide analysis runs in the background, but it can not yet show errors in the text editor. As you might deduce from the previous paragraph, the text editor is not yet ready for out-of-process.

For different Visual Studio versions, we have different abstractions, and they all integrate with the Visual Studio editor, error stripe, gutter marks, highlighters, etc. Dropping support for Chocolatey is really disappointing. Who wants to go back to slow visual studio? Hello Aaron! We are working on cross-platform profiling. We aim for this year, but no hard ETA yet. As for dotPeek functionality, Rider has already been able to navigate to decompiled sources.

Now my ForTea t4 template extension just stopped working. Is it by design that I now have to explicitly start a new test session AND reconfigure my continuous testing behaviour after each reopen of a solution? The previous behaviour of continuous testing was that you switched it ON for a solution and it remained on.

So when you opened a solution your continuous testing session was immediately active, after building I immediately got test results. Hello Martijn! Please note that Unit Test Sessions window is invisible on solution start, but continuous testing keeps working. Thanks, save and restore session did the trick. Did that behaviour change in this update or is it just needed because of new stuff? Nothing too bad, just glad it works now, just wondering.

Congrats on the release. This worked in previous version. Any ideas? The jump from This appears to be a significant regression performance wise. The performance issues largely vanish if I suspend Resharper Mike We are so sorry to hear you are experiencing the performance issue using R Disappointing, a lot of performance issues with R Everything is slower with this version… Downgraded to ReSharper 8. It also keeps track of plugin updates, and offers to update plugins when a new version is available.

This is where my problem has arisen. A particular plugin I use GoToWord has been updated, and the latest version 0. I cannot work out any way to roll back to the previous good version 0. But this fails at the dependency resolution phase, presumably because ReSharper isn't known to the regular NuGet:. Or is there some other way to install an old version of a plugin? Sadly, we didn't implement support for installing older versions of a plugin. But you should be able fake it manually, by editing the packages.

If you restart VS now, and go to the extension manager, you should get prompted that some extensions aren't installed, and clicking the package restore button should download and install the right version.

Have you reported the issue on the project's GitHub page? Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. How can I install an old version of a ReSharper plugin?