Dotnet logo

The .NET Tools Blog

Essential productivity kit for .NET developers


ReSharper Ultimate 2019.3.2 is Out!

The ReSharper Ultimate 2019.3.2 bugfix update was published a moment ago and is ready for you to download!

Let me highlight the most important things in ReSharper 2019.3.2:


  • ReSharper’s Unit Test runner can now discover NUnit parameterized tests after updating the NUnit3TestAdapter package to version 3.16.
  • The Localization Manager has been refined:
    • There are new toggles, “Show Only Localizable String Resources” and “Order by Resource File Path“.
    • Better handling for non-string resources.
    • States of all checkboxes and toggles are persisted on reopening the Localization Manager tool-window.
    • Adding new cultures is much easier now, thanks to code completion.
  • Blazor support has been improved with better code analysis, navigation, and Find Usages.
  • There are several improvements in Inlay Hints:
    • Type hints for recursive patterns.
    • Enhanced tooltips for type hints.
    • Inlay Hints no longer interfere with Ctrl+Click execution on an identifier next to a hint.
    • A few performance optimizations.
  • InspectCode and dupFinder from ReSharper command-line tools work again.

For the other latest fixes in ReSharper, please refer to this list

The other tools in ReSharper Ultimate get updates too:

  • dotTrace 2019.3.2 fixes hanging unit test sessions under profiling. See the full list of fixes here.
  • ReSharper C++ 2019.3.2 has a solid set of bugfixes.

Last but not least, we’ve introduced the newest version of our unit testing framework – dotMemory Unit 3.1, which supports .NET Core versions 3.0 and 3.1.
To install ReSharper Ultimate 2019.3.2, download the build from, or run ReSharper | Help | Check for Updates right in MS Visual Studio.

Comments below can no longer be edited.

17 Responses to ReSharper Ultimate 2019.3.2 is Out!

  1. Mike-EEE says:

    February 12, 2020

    Congratulations on all the improvements. I hate to ask but… will this require all new version/releases for extension authors even though this is considered a bug fix release?

    We are chronicling the grief of this process here:

    We are essentially having to wait 4-6 weeks after a R# release before we can fully enjoy all the extensions we had with the previous release.

    Thank you for any consideration towards addressing this rather ugly pain point for those of us who REALLY use your product. 🙂

    • Mike-EEE says:

      February 12, 2020

      Btw the 502 Bad Gateway problem still occurs when posting a comment on your blog.

    • VS Rules says:

      February 14, 2020

      Investment in ReSharper is being greatly reduced in favour of Rider for strategic reasons. So I would not expect to see any solutions to fundamental design miscalculations like this one – ever.

  2. Erik says:

    February 14, 2020

    Another update that made me go “Please, please please… oh… nothing about ‘Major performance improvements’ :'(”

    I really wish I could reactivate Resharper, but the performance cost is too big. It’s a weird feeling disabling such a great extension and go “Wow! What a relief!”

    I miss Resharper 🙁

  3. Chet says:

    February 14, 2020

    I suggest you stop working on new features until you fix the abysmal performance issues

    • Simon Vane says:

      February 17, 2020

      I couldn’t agree more. It’s unusable in Visual Studio 2019.

    • Tim says:

      February 19, 2020

      Absolutely agree. Performance with VS 2019 is appalling and unusable.

    • Maria Pleskunina says:

      February 25, 2020

      We are very focused on improving ReSharper performance, please take a look at ReSharper 2020.1 Roadmap:

  4. Eliran Teller says:

    February 17, 2020

    I’m currently having extremely low performance with the new update.

    • angelina.elycheva says:

      February 18, 2020

      Hello Eliran,

      Could you please collect a performance snapshot for us as described in the following article – Please specify the steps that lead to the problem in the snapshot details.
      Thanks in advance.

      • Eliran Teller says:

        February 19, 2020

        OK, I’ll try to do that when I have some free time 🙂
        Currently downgraded to 3.1 and seems to be better.

  5. Simon Vane says:

    February 17, 2020

    This product is simply not usable with Visual Studio 2019. It’s a shame not to be able to use it because it has good functionality. A

    Are you going to fix the performance issues?

    • angelina.elycheva says:

      February 18, 2020

      Hello Simon,

      Sorry to know you’ve experiencing performance problems.
      To begin with, I’d like to assure you that we do our best to fix the performance issues. All user performance reports are considered and fixed as top priority issues.
      Could you please specify cases when you experience low performance? Some specific steps causing the issue, type of project you are working in or any other detail shedding light on the problem will be helpful.
      Also, we’d be grateful if you collect a performance snapshot for us as described in the following article –
      Thank you.

      • Tim says:

        February 19, 2020

        I can’t believe you keep asking these questions!
        You know what the performance is like, it’s been widely reported!

        • Rick says:

          February 20, 2020

          Of course they need more information to see what’s different on your system.
          I’m not seeing any performance issues on my setup.

          • Nash says:

            February 22, 2020

            Could you please share your setup specs? I’m sure a lot of people commenting here for performance issues will be interested to know just how much hardware they have to throw at ReSharper to get the performance u’re experiencing.

Discover more