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.

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

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

  1. Matvei Stefarov says:

    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: https://youtrack.jetbrains.com/issues/RSRP?q=Fix%20versions:%202017.1.1%20and%20State:Fixed%20

  2. Dev says:

    Thank you!

  3. Ravi says:

    Thanks for the quick turnaround. Much appreciated.

  4. Pingback: ReSharper Ultimate 2017.1 – Alles zur neuen Version

  5. Alex says:

    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.
    Thanks

  6. Patrick Blackman says:

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

  7. Pingback: Dew Drop - April 17, 2017 (#2459) - Morning Dew

  8. Mike-EEE says:

    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?

Leave a Reply

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