ReSharper Ultimate 2017.3.2 bugfix is here

Alexander Kurakin

Our latest and greatest ReSharper Ultimate 2017.3 has just received the second bugfix update – download ReSharper Ultimate 2017.3.2!

ReSharper Ultimate 2017.3.2 bugfix update

We added more than 100 fixes in this build. Here are the notable changes:

  • Returned MSTest support for UWP and CodedUI tests.
  • Fixed “Inconclusive: Test not run” issue when running/debugging MSTest unit tests.
  • Improved support for Razor Pages.
  • Fixed bogus unresolved symbols in a React and Redux project.
  • Lots of improvements/fixes in the new code formatting engine.
  • Fixed a ReSharper integration issue for Visual Studio 2017 on Windows 10 machines.
  • Surround typing does not interfere with closing brace overtyping anymore.
  • The Sort by drop-down list and the Switch to Constraint View icon are back on the File Layout page.
  • Symbols from .NET Framework 4.7.1 projects are now properly resolved in .NET core projects.
  • Lots of improvements in the Generate engine.
  • A fix for “Configure settings to improve performance” message in the VS notifications panel.
  • A bunch of fixes in refactorings.
  • Several fixes/improvements in Navigation/Find Usages logic and presentation.
  • Debugger extensions support Visual Studio 2010.

Apart from all that, the ReSharper 2017.3.2 update has a heap of improvements for hiDPI support and performance/stability fixes in TypeScript and C#.

ReSharper C++ 2017.3.2 includes a significant number of performance and stability fixes, enhanced code analysis, and Generate action improvements. Please refer to this list to see all fixed issues.

You can either download the build from our site or use the ReSharper | Help | Check for update menu in Visual Studio.

Comments below can no longer be edited.

14 Responses to ReSharper Ultimate 2017.3.2 bugfix is here

  1. Joshua Morgan says:

    February 2, 2018

    Noticed right away that my TypeScript in React stops warning me about invalid fields that were in fact valid. Good job! Sadly, the generic types are still confusing the system. For instance, the below will tell me that id and title are unknown properties.

    interface ITitleProps {
    id?: string;
    title: string;

    class BaseTitle extends React.Component {
    constructor(props: T) {

    render() {
    return (



  2. Dave Cousineau says:

    February 6, 2018

    Since I updated, I’ve noticed that highlighting no longer works on Console.WriteLine, string.Format, etc. (the {0} {1} markers don’t turn green).

    • Alexander Kurakin says:

      February 7, 2018

      @Dave What type of project do you see it in – a classic .NET, a .NET core, a .NET Standard?

      • Dave Cousineau says:

        February 12, 2018

        VS 2013, classic .NET I think.

        • Alexander Kurakin says:

          February 21, 2018

          Thanks for the reply, does the issue happen in a newly created solution?

          • Dave Cousineau says:

            February 21, 2018

            Hmm, no. If I create a new .NET 4 Console Application, the string.Format highlighting works.

            With two instances of VS2013 open under the same user, my old solution does not work, and the newly created one does work.

          • Dave Cousineau says:

            February 23, 2018

            Actually… it works for my own methods that use StringFormatMethodAttribute. It just doesn’t work for Console.WriteLine, StringBuilder.AppendFormat, etc.

            Is there an easy fix for this?

          • Dave Cousineau says:

            February 25, 2018

            I’ve just upgraded to VS2017 and it still has the same problem. I tried deleting my .suo file but that broke ReSharper and I had to run a repair install.

          • Dave Cousineau says:

            February 27, 2018

            Well I guess now that I have string interpolation I can just use that instead of fixing this.

          • Dave Cousineau says:

            March 8, 2018

            Thanks for nothing I guess

            • Alexander Kurakin says:

              March 8, 2018

              @Dave Please accept my apologies for not replying you earlier, I was out of office. Please file a new request here, the blog is not the right place to continue the investigation, we will need some log files and screenshots, so, a support request will cover all these things.

  3. QJ says:

    February 28, 2018

    DotCover integration with VS2017 does not work for me. The DotCover menu does not show up after installation and I have tried to reinstall resharper 2017.3.2 but still no luck. VS2015 has no issue for the integration with dotcover.

    Has anyone encountered the same issue?


Subscribe to .NET Tools updates