ReSharper Ultimate 2019.2.3 Bugfix Is Here!

Posted on by Alexander Kurakin

Moments ago we published a new bugfix – please welcome ReSharper Ultimate 2019.2.3. It delivers highly requested support for the .NET Core 3.0 release build, which was released earlier, for all the tools in the ReSharper Ultimate family!
RU2019.2-splash@2x

In addition, ReSharper 2019.2.3 includes about 30 resolved requests such as these:

  • Lots of fixes related to the MSBuild-based project model.
  • “Override” code completion does not touch members above the completed element anymore.
  • Typing a single quote in code comments does not insert a pair of single quotes anymore.

Other tools from the Ultimate pack have lots of fixes as well:

  • ReSharper C++ 2019.2.3 delivers several fixes to better support the MSBuild-based project model while loading C++ projects. The Parameter info popup now appears automatically, and focus is not lost anymore after you apply the “Generate implementation” quick-fix. The full list of fixes is here.
  • dotTrace 2019.2.3 fixes various issues.
  • dotCover 2019.2.3 fixes a number of important issues related to dotCover’s console runner.
  • dotMemory 2019.2.3 fixes issues related to unsupported types and bugs in the profiler core.

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

Comments below can no longer be edited.

3 Responses to ReSharper Ultimate 2019.2.3 Bugfix Is Here!

  1. Troy says:

    October 21, 2019

    My word! Thanks guys so much for this update. Never been disappointed with the support and the prompt bugfixes from JetBrains.

  2. Jeff Chen says:

    November 14, 2019

    I just find out that ‘Rename’ is not working anymore after upgrading to latest version.

    • Maria Pleskunina says:

      November 14, 2019

      Hi Jeff, please try clearing caches via `ReSharper | Options | Environment | General | Clear caches` and check the problem once again. Does it work for you?
      If the problem occurs again, we’d be grateful if you let us know about it.

Subscribe

Subscribe to .NET Tools updates