ReSharper Ultimate 2018.2.1 is released!

A week ago, we published the ReSharper Ultimate 2018.2 release. Today it’s time for the first bug-fix release – please welcome ReSharper Ultimate 2018.2.1!

In ReSharper 2018.2.1, we have fixed the annoying bug that affected NUnit test framework support when all unit tests from a test fixture were triggered after you ran just a single one. In addition, we’ve fixed several ReSharper Command Line Tools bugs, the most important one being InspectCode tool hanging on some solutions. For the full list of fixes, please see this link.

Other ReSharper Ultimate tools have addressed some bugs as well: see the fixes in ReSharper C++ 2018.2.1 and the fixes in dotTrace 2081.2.1.

You can download the build from our site or use ReSharper | Help | Check for Update.

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

5 Responses to ReSharper Ultimate 2018.2.1 is released!

  1. Jeremy Morton says:

    I’m not sure yet if this is due to extensions, but with 2018.2.1, I’m getting a lot of incorrect complaints about extra spacing around the conditional operator ( ? : ) and within braces, even though my formatting setting have these set to have spaces.

    Is anyone else seeing this?

    https://www.jetbrains.com/help/resharper/2018.2/BadSymbolSpaces.html
    https://www.jetbrains.com/help/resharper/2018.2/BadDeclarationBracesLineBreaks.html

  2. Martin Zindler says:

    I hade the same problem (debugging a single test case), but using XUnit instead of NUnit.
    THIS is NOT fixed in 18.2.1!!
    Still the same behavior, onlz waz to start a single “InlineData” Theory is to use the ReSharper Testrunner with right-click. And it still starts ALL test cases.

    Please FIX THIS asap.

    Best // Martin

  3. Pingback: Dew Drop - August 31, 2018 (#2794) - Morning Dew

Leave a Reply

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