ReSharper Ultimate 2017.1.1 fixes MSTest discovery, C++ issues

We have a bug-fix update for you as ReSharper Ultimate 2017.1.1 is now available for download.

You should definitely get this release if you have installed the latest Visual Studio 2017 update (April 6), and then when you tried to run your MSTest suite, you saw ReSharper telling you this:

Visual Studio 2017 outdated? Not really

Turns out that the latest Visual Studio update reverted a prior API change in a way that we didn’t expect, which kind of explains why ReSharper took the absolute latest Visual Studio build for an outdated one. The problem is now fixed, and you can run your MSTest suites again.

Apart from fixing the unit test runner issue, this update includes a small set of fixes in ReSharper C++.

dotMemory, dotCover, dotTrace and dotPeek have not received any bug fixes so far.

Comments below can no longer be edited.

10 Responses to ReSharper Ultimate 2017.1.1 fixes MSTest discovery, C++ issues

  1. Avatar

    Matvei Stefarov says:

    April 7, 2017

    Thanks for a quick patch. This also fixed loading for one of my bigger solutions, which used to freeze whole VisualStudio with ReSharper 2017.1 enabled. ReSharper fixes:

  2. Avatar

    Dev says:

    April 7, 2017

    Thank you!

  3. Avatar

    Ravi says:

    April 8, 2017

    Thanks for the quick turnaround. Much appreciated.

  4. Avatar

    Alex says:

    April 10, 2017

    Hi, I installed this update and detect that behavior F5 button is changed.
    Before upgrade when I pressed F5 the behavior of VS was: Detect if something is changed -> Build -> Run
    Now I pressed F5 -> Provide only Run
    So there is no detecting a new changes and build them before Run.
    Now I should pres Ctrl+Shift+B to build and than press F5 button.
    The same problem has all our development team 🙁
    Any Idea?
    Some detail:
    VS2017 (26403.0)
    Resharper 2017.1.1 built on 2017 April 07.
    Primary use Resharer build.

  5. Avatar

    Patrick Blackman says:

    April 10, 2017

    Thanks for the excellent service, wish other vendors had your standards.

  6. Avatar

    Mike-EEE says:

    April 17, 2017

    OK I just took the jump and installed this puppy.

    In 2016 exceptions that occurred during unit tests were output in the output window.

    That no longer appears to be the case. Is there a setting for this somewhere, perhaps?

    • Alexander Kurakin

      Alexander Kurakin says:

      April 17, 2017

      @Mike-EEE Do you use VS2015+”.NET Core”+xUnit combo?
      If so, there is this issue about a regression in R# 2017.1.1.

      • Avatar

        Mike-EEE says:

        April 17, 2017

        May the record show that I, too, have red hair. 😛

      • Avatar

        Mike-EEE says:

        April 20, 2017

        Any idea when 2017.1.2 will be available? Testing is a bit painful now. More than usual. Knowing why a test failed is a bit useful.

        • Avatar

          Jura Gorohovsky says:

          April 20, 2017

          Mike, 2017.1.2 is scheduled for next week.

Discover more