ReSharper Ultimate 2018.3.1 bug-fix update is here

Alexander Kurakin

Today, we invite you to download the first bug-fix build for ReSharper Ultimate 2018.3 release – ReSharper Ultimate 2018.3.1.

This bug-fix update resolves the following issues:

  • ReSharper Build couldn’t build a project if MSBuild was installed as part of Visual Studio 2019 Preview 1 (RSRP-472694).
  • Visual Studio froze on JavaScript debugging (RSRP-472802).
  • Inconsistent default state around ‘Inconsistent Naming‘ inspection (RSRP-472812).
  • A false positive for NUnit TestCase (RSRP-472787).
  • Unit test coverage highlighting is not shown for projects targeting .NET Framework 3.5 and lower (DCVR-9525).
  • False “Cannot convert type” error for Promise in TypeScript.
  • Find Usages did not process bodies of #define macros when looking for textual occurrences (RSCPP-24977).
  • Remove unused parameter” quick-fix was broken in C++ (RSCPP-25094).

Download the build from our site or via Toolbox App, or run ReSharper | Help | Check for updates right in Visual Studio.

Comments below can no longer be edited.

7 Responses to ReSharper Ultimate 2018.3.1 bug-fix update is here

  1. Dew Drop - December 28, 2018 (#2868) - Morning Dew says:

    December 28, 2018

    […] ReSharper Ultimate 2018.3.1 bug-fix update is here and Rider 2018.3.1 bug-fix update is here (Alexander Kurakin) […]

  2. John M says:

    December 29, 2018

    That’s great! Now can you fix the fix to actually work with VS 2015?
    After installing it I cannot make a build using R#.
    It does seems to build OK using VS build instead.
    Otherwise it says “Can’t connect to msbuild process”.

    • Alexander Kurakin says:

      December 29, 2018

      @John, Have you experienced the same issue before installing R# 2018.3.1? Do you have VS2019 Preview installed on the same machine?

  3. Calvin Pomerantz says:

    January 3, 2019

    I am experiencing problems with VS 2015 as well. Inline inspections are not working, and many options are greyed out in the ReSharper menu in the toolbar.

    These problems exist in 2018.3.0 and 2018.3.1. I do not have VS 2019 preview installed on my machine, but I do have VS 2017 installed (we are working on upgrading our project to 2017).

  4. Mathijs Bakker says:

    January 8, 2019

    Hi y’all Brainers! Any update on dotCover for MacOS, yet?
    Will there be any estimated roadmap published online?

  5. Dmitriy says:

    January 15, 2019

    ReSharper unit test runner (starting with 2018.3) set AppDomain to “Entryway” – it breaks our tests.
    2018.3.1 still has the issue.
    Do you have the issue registered and any idea when it’s going to be fixed?

    More details about the issue https://resharper-support.jetbrains.com/hc/en-us/community/posts/360001516439-ReSharper-unit-test-runner-and-AppDomain-name-issues

  6. Fedor Buyvol-Kot says:

    January 17, 2019

    @Dmitriy, the discussion about AppDomain name can be found in this report: https://youtrack.jetbrains.com/issue/RSRP-472316

Subscribe

Subscribe to .NET Tools updates