ReSharper Ultimate 2018.1.1 bug fix update is here!

Hello from JetBrains! We have something interesting for you today. A few moments ago, we published the first bug fix update for our first release of the year – ReSharper Ultimate 2018.1.1.

Below, you can find a list of the notable changes:

  • ReSharper’s shell loading has been optimized to decrease Visual Studio’s startup time. Now it is faster, and we have mostly got rid of the Visual Studio yellow notification about the slowness of starting up ReSharper. There is still a yellow box about total unresponsiveness, but it is going to take another step to fix, which we are working on right now.
  • Lots of fixes and optimizations around XAML in WPF and Xamarin.Forms projects which were broken after installing Visual Studio 15.7.
  • Rename refactoring for a private field in a C# file does not look through Razor files anymore. In this update, renaming a private member doesn’t take longer than it should.
  • ReSharper now correctly defines the latest C# language version after installing the Visual Studio 15.7 update. No more “C# 7.1 language feature” false positive errors.
  • Several fixes in ASP.NET MVC support. Moreover, this build is shipped with the updated External Annotations package to support the latest MVC NuGet package (version 5.2.6), it gets back the navigation from a Controller to a View.
  • A fix for the “Cannot apply indexing to an expression false error message in VSTO Excel application.

Apart from that, there are a bunch of fixes for Code formatting engine, Unit Test runner, Refactorings, and Navigation/Find Usages. To see the full list of fixes, please refer to the YouTrack page.

Also, we’ve implemented a few small features:

  • JetBrains Annotations finally support .NET Standard projects.
  • The tab size is now taken into account on applying line wrapping.
  • Find Usages now supports deconstructs.

ReSharper C++ 2018.1.1 has a lot of fixes as well: support for Boost.Test from Boost 1.67, fixed regressions with missing results in Find Usages, and incorrectly deduced return types in lambdas and functions with an auto return type. More fixes are here.

dotCover 2018.1.1 now correctly updates Hot Spots view in Unit Test Coverage tool window after changes in solution assemblies, and fixes the issue in updating of a coverage snapshot which could have led to an inconsistency in the coverage data and errors in the graphical coverage presentation.

Download ReSharper Ultimate 2018.1.1 or use ReSharper | Help | Check for update.

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

33 Responses to ReSharper Ultimate 2018.1.1 bug fix update is here!

  1. Mike says:

    It’d be great if you guys could add in some C#7.3 stuff. Right now I’m getting “errors” on lines that use structs with an unmanaged constraint (C#7.3 generic constraint), and it makes error tracking no better than if I didn’t have Resharper installed.

    Alternatively, since they (i.e. the .NET guys) are updating the language a breakneck pace, it’d also be great if I had some way to say “ignore this error please”, so I can at least turn off the false positives, at least until official support is added.

    • +1 for “do not show this message again for ## days”

    • Chris says:

      I had to uninstall ReSharper because my whole code was getting marked as errors when using the new unmanaged feature on generics.

    • Alexander Kurakin says:

      @Mike, C# 7.3 support will be added in ReSharper 2018.2 release cycle.
      To suppress errors in the text editor, you can use “// ReSharper disable errors” comment which hides all errors below till “// ReSharper restore errors” comment.

      • Chris says:

        thanks but i’ll pass. not going to comment // ReSharper disable errors on 100+ lines just because it doesn’t understand “unmanaged”

  2. That’s a great list for a patch release!

  3. Pingback: ReSharper Ultimate 2018.1.1 bug fix update is here!  | OPC Diary

  4. Antony Corbett says:

    Thanks for the update. The StyleCop extension is still at version 2018.1 and some of the functionality no longer works (e.g. it correctly identifies wrongly positioned “using” directives but will not fix them).

  5. des says:

    That’s cool and all but when will Rider be part of Resharper Ultimate?

    • Alexander Kurakin says:

      @des, we have no plans to include Rider to “ReSharper Ultimate” license. You might upgrade “ReSharper Ultimate” to “ReSharper Ultimate + Rider” one, it is quite cheaper than purchasing “ReSharper Ultimate” and “Rider” licenses separately. Please refer to | ReSharper Ultimate | Tick “Include Rider, Cross-platform .NET IDE” checkbox

  6. Michael Hansen says:

    Been a ReSharper user for 10-12 years or so, and ReSharper has always resulted in some performance degradation in VS, but nothing I couldn’t live with.

    But for the first time ever I had to downgrade to the previous version again due to massive performance degradations in the editor (just typing freezes, intellisence extremely slow etc.).

    Downgrading to 2018.1 fixed the issue.

    Just “plain” C# (7.2) in fully upgraded VS2017.

    • clive Hodgson says:

      I’ve got performance issues with 2018.1.1. How do you downgrade to 2018.1? Is there is an option somewhere or do you have to completely remove and then reinstall the older version?

      • Alexander Kurakin says:

        You may always download any previous ReSharper versions from page.

        • clive Hodgson says:

          I specifically asked how to downgrade?

          So I downloaded 2018.1 from the link you provided and ran it but it failed for each of the 3 versions of VS I have installed.

          So i uninstalled everything I found for Resharper in the Control Panel and re-ran installer for 2018.1 and it failed for VS2010 and VS2013 and only installed for VS2015. Thankfully I only need it in 2015 at present for the project I’m on but I’ll need to sort it for the other 2 versions for supporting older products. I could do without this hassle if you had explained how to do a downgrade properly…..

      • Lasse Vågsæther Karlsen says:

        Yeah, I got massive problems with both 2018.1 and 2018.1.1. 2018.1.1 was slightly better than 2018.1 but still bad in terms of performance.

        In 2018.1, whenever the intellisense popup was shown Visual Studio ground to a complete halt for 5-10 seconds before allowing me to continue selecting an item or typing. I also experienced frequent crashes in the editor which required a restart of Visual Studio 2017.

        In 2018.1.1 the hitches are smaller, ie. it only pauses for about half a second, but they come all the time, for instance, in the following line:

        var genericTypeDefinition = typeInfo.GetGenericTypeDefinition();

        I get hitches about every 2-3 letters which makes programming a *very* jarring experience. Since autocomplete and things seems to run async to the editor experience, any attempt at just continuing to write while it pauses will frequently end up with completely broken code due to completion kicking in about a second after the code it completed, so I frequently see things like:

        instance.SomeMethod( <– this is where ReSharper figures out that it can help, actually it detects it slightly before and shows a list of all methods that start with SomeMethod, the ( triggers the "complete this" though, which starts it thinking

        instance.SomeMethod().ProcessRe <– this is when ReSharper has come to a conclusion

        instance.SomeMethod().ProcessReSomeLongerMethod() <– this is what I end up with

        I've had to revert back to 2017.3.5 for the time being but this means I have to pause working on my .NET Standard class libraries since 2017.3.5 is unable to run unit-tests for .NET Core projects.

    • Net says:

      I see the mentioned performance issues too.

    • Matt Honeycutt says:

      I’m seeing major performance issues with this version, too. Downgrading until things are fixed…

    • Alexander Kurakin says:

      We’ve fixed it in ReSharper Ultimate 2018.1.2 bug fix update

  7. Sorry to hear that, Michael.

    Would you mind trying 2018.1.1 again and collect a performance snapshot while typing lag occurs? General process is described here ?

    PS: We are starting a R# performance series with more background – first post is live here:

  8. Pingback: Dew Drop - May 29, 2018 (#2734) - Morning Dew

  9. Vasily says:

    Would be nice to have the link to this page in the update dialog in VS to be able to quickly check what’s in there and e.g. avoid wasting time on upgrade and downgrade if there are known issues such as the one reported above.

  10. James Legan says:

    So this was a fun surprise after updating to 2018.1.1, rendering the IDE unusable (the screen redraw it is in does not allow for any mouse activation, so cannot close tables/respond to the warning) until uninstalling and reverting to 2018.1.

Leave a Reply

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