ReSharper Ultimate 2016.3.1

Looking for a bugfix release? We have one! ReSharper Ultimate 2016.3.1 is now available for download. This update addresses a selection of issues in ReSharper and ReSharper C++.

ReSharper 2016.3.1 is mostly about integrating into Visual Studio 2017 RC. We’ve received a lot of complaints about 2016.3 not detecting a Visual Studio 2017 RC installation. In all cases, repairing the Visual Studio installation would fix the issue, and based on this experience, we’ve updated the installer to detect (and warn about) incomplete Visual Studio installations.

Other than that, the new ReSharper fixes a couple of code analysis regressions, issues with discovering .NET tests in certain scenarios and running Jasmine tests, and addresses some false red code reports in PCL projects and elsewhere. Here’s the full list of ReSharper fixes for your reference.

ReSharper C++ 2016.3.1 improves an assortment of code inspections, quick-fixes, unit testing, IntelliSense and XML documentation usage scenarios. Here’s the full list of ReSharper C++ fixes.

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

6 Responses to ReSharper Ultimate 2016.3.1

  1. Pingback: ReSharper Ultimate 2016.3.1  | OPC Diary

  2. Pingback: Dew Drop - December 26, 2016 (#2391) - Morning Dew

  3. Pac says:

    Hi,
    Wanting to install some extensions, but R#’s Extension Manager only gets an empty list from configured “.NET Products Gallery” source (https://resharper-plugins.jetbrains.com/api/v2/curated-feeds/Wave_v7.0/)
    Any ideas?
    Thanks in advance.

    • Jura Gorohovsky says:

      Pac, are you facing this issue with ReSharper 2016.3.x? Were you facing similar issues before installing 2016.3.x?

      • Pac says:

        Hi Jura,
        I was facing this issue with previous installations. So further investigating, I discovered that my OS setup lacked some root CA certificates that prevented to connect to R#’s Extension Gallery. The error log generated by trying to repair my R# installation helped to discover the root cause.
        Thanks again.

  4. Pingback: Auf dem Weg zu ReSharper Ultimate 2016.3 - entwickler.de

Leave a Reply

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