ReSharper Ultimate 2019.2.4 and Rider 2019.2.4 Bug Fixes Are Here!

Even though the new major 2019.3 releases for both ReSharper Ultimate and Rider have both come out, we have not forgotten about our users who still use the summer 2019.2 releases. And today, we’ve published a new set of bug fixes: ReSharper Ultimate 2019.2.4 and Rider 2019.2.4.

ReSharper Ultimate 2019.2.4 fixes the caches issue that prevents Find Usages from getting any results. So, if nothing happens when you call the Find Usages or Find Usages Advances actions and clearing your caches is the only thing that helps, this build is right for you. In addition, this build has a fix for ReSharper extensibility that improves the installation procedure for several extensions, e.g. the Enhanced Tooltip extension. 

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

Rider 2019.2.4 brings back feature-rich support for F# script files (.fsx) on macOS and Linux, which was accidentally broken in the 2019.2 release. 

Possible ways to get the 2019.2.4 bug fix:

  • Download and install it from www.jetbrains.com.
  • Inside Rider, select Help | Check for updates.
  • Use our Toolbox App.
  • Use this snap package from the SnapCraft store (if you use a compatible Linux distro).
This entry was posted in Releases and tagged , , , , , . Bookmark the permalink.

4 Responses to ReSharper Ultimate 2019.2.4 and Rider 2019.2.4 Bug Fixes Are Here!

  1. Sergio Pedri says:

    Is there any ETA at all on the support for x:Bind functions in XAML?
    The issue is here: https://youtrack.jetbrains.com/issue/RSRP-460197

    It has been opened for 4 years now with no official response yet.
    That missing feature is a game breaker when working on UWP apps.

    Thanks, keep up the good work!

  2. Richard says:

    When will the update be properly “live”? Currently “Help -> Check for updates” returns “All products are up to date”.

    • Richard says:

      Never mind – just noticed it’s an update for 2019.2, not 2019.3! :)

      • Alexander Kurakin says:

        Yes, this update is for the 2019.2 release. So, if you are on 2019.3 – you have to wait for 2019.3.2 bugfix build which we are going to publish it at the beginning of February.

Leave a Reply

Your email address will not be published. Required fields are marked *