ReSharper Ultimate 2017.2.2 available

A new minor update for the ReSharper Ultimate family is available for download!

ReSharper 2017.2.2 fixes the annoying code completion bug with duplicate parentheses (RSRP-466206) and addresses the remaining known issues when completing сode with Tab (RSRP-466421). It also improves the null checking quick-fix behavior (RSRP-464225) and correctly resolves .NET Standard 2.0 libraries in Visual Studio 2017 version 15.4 preview 4 (RSRP-466417). See all fixes in ReSharper 2017.2.2.

ReSharper C++, dotCover, dotTrace, dotMemory, and dotPeek 2017.2.2 have been updated solely for compatibility reasons and include no significant changes.

In case you were affected by the issues mentioned above, we recommend that you download and install ReSharper Ultimate 2017.2.2.

Note to ReSharper EAP users: we’re already working on version 2017.3 and will open early access soon!

Comments below can no longer be edited.

7 Responses to ReSharper Ultimate 2017.2.2 available

  1. Avatar

    Bill says:

    October 10, 2017

    We are still seeing issues with methods flagged with “Method XXX not used” but “Find Usages” finds one or more of the method in use. Last two updates seem to have exacerbated the problem.

  2. Avatar

    Ekaterina Zharova says:

    October 11, 2017

    Hi Bill,

    Do you use any of ReSharper plugins? Could you please file a request on YouTrack and provide us more info there about the issue.

  3. Avatar

    Peter Allgaier says:

    October 18, 2017

    I have the same issue. I recognize it on member variables starts with an underscore!

  4. Avatar

    peterallgaier says:

    October 18, 2017

    I have the same issue. I recognized this problem by membervariables starting with an underscore!

  5. Avatar

    Cory Sylvan says:

    October 18, 2017

    I take pleasure in, lead to I found exactly what I was taking a look for. You have ended my four day long hunt! God Bless you man. Have a great day. Bye

  6. Avatar

    jm says:

    November 30, 2017

    The C++ inspection “Parameter may be const” is not great. It should not apply to the “passed by value” parameters, as making them const is useless, and considered pointless by many developers.

    So, I think this rule should be divided into
    “(passed by value) parameter may be const”
    “(passed by pointer or reference) parameter may be const”

    In case of “passed by pointer”, this latter rule should apply to the pointed value, not to the pointer (which is actually passed by value, and would then be affected by the former rule)

    • Avatar

      Igor Akhmetov says:

      December 4, 2017

      Parameters in this regard can be treated the same as local variables, so whatever guidance you use when declaring local variables as const can be applied to parameters too.

      That said, we’ve got a few complaints about this inspection, and lowered its default severity in the 2017.3 release.

Discover more