ReSharper Ultimate 2016.2.1 is available

Posted on by Jura Gorohovsky

We have just published a bug fix update to ReSharper Ultimate 2016.2.

This release contains a fine selection of 70 hand-picked bug fixes across ReSharper, ReSharper C++ and dotCover.

Please download and enjoy ReSharper Ultimate 2016.2.1!

Comments below can no longer be edited.

10 Responses to ReSharper Ultimate 2016.2.1 is available

  1. New ReSharper update. - How to Code .NET says:

    September 12, 2016

    […] on September 11, 2016 submitted by /u/JimboSchneider [link] [comments] Leave a […]

  2. ReSharper Ultimate 2016.2.1  | OPC Diary says:

    September 12, 2016

    […] 情報源: ReSharper Ultimate 2016.2.1 is available | ReSharper Ultimate Blog […]

  3. ReSharper Ultimate 2016.2 ist final – das ist neu - entwickler.de says:

    September 13, 2016

    […] das ReSharper-Ultimate-Team via Blogpost bekanntgibt, steht mit ReSharper Ultimate 2016.2.1 das erste Maintenance-Update für das kürzlich […]

  4. Vladimir Kozlov (ai_enabled) says:

    September 13, 2016

    Thanks for update!
    Unfortunately, it breaks code cleanup for me – ReSharper is adding “private” modifier to the ~Finalizer() signatures…

    • Vladimir Kozlov (ai_enabled) says:

      September 13, 2016

      It’s also adding “private” modifier for static constructors (which is also leads to the compilation errors).
      Will you provide a hotfix?

      • Jura Gorohovsky says:

        September 13, 2016

        Looks like we will.

        Thanks for bringing this up, Vladimir.

  5. Dew Drop - September 13, 2016 (#2327) - Morning Dew says:

    September 13, 2016

    […] ReSharper Ultimate 2016.2.1 is available (Jura Gorohovsky) […]

  6. Richard says:

    September 13, 2016

    Your link to “70 hand-picked bug fixes” returns 65 results.

    • Jura Gorohovsky says:

      September 13, 2016

      Right, this is probably due to visibility of some of the issues.

      • Stephen says:

        September 14, 2016

        It’s probably better to either change the post or be sure of your answer when your customers have been super tolerant of how long bugs take to fix .. IMHO

Subscribe

Subscribe to .NET Tools updates