ReSharper Ultimate 2019.2.2 is Out!

The new bugfix for ReSharper Ultimate is available – say hello to ReSharper Ultimate 2019.2.2.

ReSharper 2019.2.2 fixes more than 50 issues and the most important ones are highlighted in the list below:

  • Code completion after the override keyword was reworked and works much better now.
  • The performance of Solution Wide Error Analysis (SWEA) in ASP.NET projects has been improved. SWEA does not take ages to finish anymore!
  • Fixed several issues in our new MSBuild-based way to build the Project Model.

To install ReSharper Ultimate 2019.2.2, download the build from or run ReSharper | Help | Check for Updates right in MS Visual Studio.

Comments below can no longer be edited.

9 Responses to ReSharper Ultimate 2019.2.2 is Out!

  1. Avatar

    FixItPlease says:

    August 30, 2019

    2019.x is unusable and very basic aspects fail to function:

    – Unable to correctly find symbols in loaded projects.
    – Unable to find/run tests.
    – Assemblies not being refreshed on builds.

    Clearing cache doesn’t work. Installing 2019.1.x doesn’t improve anything. Playing around with settings is overall ineffective.

    So then why would I use ReShaper? At least before with 2018.x it was SLOW /and/ USEFUL. Now it’s just SLOW and NOT USEFUL. I can’t seem to install 2018.3 to try and ‘revert this mess’ due to a HTTPS error when the web installer when it attempts to download packages.

    I only have around 15/300 projects loaded, and still ReSharper failure. Disappointing.

    • Avatar

      Maria Pleskunina says:

      August 30, 2019


      Thanks for your feedback. I’m sorry to hear you’re facing some problems with ReSharper.
      What ReSharper version do you have installed now? Is it R# 2019.2.2? If so, please try disabling “Read solution model directly from project/solution files” in “ReSharper | Options | Environment | General”, reopen the solution and re-check problems.
      If problems persist, please contact support and provide more details about them (e.g., some screenshots can be useful). To contact us you can use the following ways: “Submit a request” in or “ReSharper | Help | Report a Bug or Submit Feedback”.
      Thank you!

      • Avatar

        Pando says:

        October 5, 2019

        This fixed it for me.

    • Avatar says:

      September 2, 2019

      We have similar issues, appearing and disappearing sporadically. It works “most” of the time, but sometimes, Resharper finds hundreds or thousands of errors while VS and dotnet commandline build the projects fine. Maybe Resharper should re-evaluate his projects when it notices that a VS build was successfull?

  2. Avatar

    Alan Costa says:

    September 3, 2019

    2019.2.2 update completely fails doing a full solution analysis for all projects/solutions.
    Any update on this?

    • Alexander Kurakin

      Alexander Kurakin says:

      September 3, 2019

      Hey Alan! Could you describe the issue in detail, please? Do you have an error message or SWEA results show lots of errors?

  3. Avatar

    John says:

    September 4, 2019

    R# 2019.2.2 with VS2019 16.2.3 is completely unusable: it runs like a slug just using the editor!!

    VS constantly complains about bad performance, “We’ve noticed that extension ‘JetBrains ReSharper Ultimate 2019.2.2’ is slowing typing performance.”

    • Avatar

      John says:

      September 5, 2019

      Using ReSharper Feedback Center to profile Visual Studio presents me with an error, “Authentication problem: Invalid resource owner credentials”

      This is even though my account name is shown in the “Submit as [….] or change account” message, and Feedback Center refuses my credentials, “Either user name or password is not correct”.

      The License Summary however shows “Properly licensed” and “Logged in”, and I am able to log out and log in again.

      • Avatar

        John says:

        September 5, 2019

        It seems that Feedback Center has not been updated wrt Two Factor Authentication, where I was unable to login directly I was able to login using a browser

Discover more