ReSharper Ultimate 2018.2.3 and Rider 2018.2.3 are released!

We’ve just published two bugfix updates, ReSharper Ultimate 2018.2.3 and Rider 2018.2.3, that you may want to install right away. Here are the fixes we’ve added in both:

In ReSharper Ultimate 2018.2.3:

  • We’ve sped up XAML support a bit (RSRP-471164).
  • 2018.2 release splashes are used instead of EAP ones (RSRP-471471).

In Rider 2018.2.3:

  • Rider correctly calculates C# language version based on the latest value in a csproj file (RSRP-471483).
  • Azure DevOps URLs in NuGet Credential Provider is supported (RIDER-19664).
  • We’ve fixed the Unhandled Exception while running Unity in batchmode (RIDER-19688).

Go ahead and install these builds at your earliest convenience. You’ll find ReSharper Ultimate 2018.2.3 and Rider 2018.2.3 on our site, or just update via Toolbox App.

This entry was posted in How-To's and tagged , , , , , , , . Bookmark the permalink.

6 Responses to ReSharper Ultimate 2018.2.3 and Rider 2018.2.3 are released!

  1. Pingback: The Morning Brew - Chris Alcock » The Morning Brew #2664

  2. Pingback: Dew Drop - September 14, 2018 (#2803) - Morning Dew

  3. Opening Visual Studio Preview with no solution immediately presented with “You can improve ‘Startup’ performance by disabling Resharper 2018.2.3

    Didn’t get the yellow bar on solution, did however get noticeable text editor scrolling lag (just mouse while up/down ) while processing assemblies was occurring. Full solution analysis is not enabled.

  4. Nathan Risto says:

    This version seems to break formatting with lines/spacing. Cleaning code does not fix and I have to go one by one using suggestions choosing “Fix Formatting Problem”

    • Jim LIttle says:

      I have had numerous issues with lines and spacing. I can’t tell exactly (yet) when/where it happens, but lines of code are being seemingly randomly moved to the previous line, resulting in code like this:

      var x = 100;x++;

      I never code two lines on the same physical line–never. But I’m seeing this all over after installing 2018.2.3. The problems ceased to occur after I suspended ReSharper in Visual Studio 2017.

Leave a Reply

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