ReSharper Ultimate 2018.3 is released!

I’m here today to present to you this year’s last major release of ReSharper Ultimate. Don’t feel like reading? Then come and grab ReSharper Ultimate 2018.3!

ReSharper Ultimate 2018.3 released

Let me show you what the ReSharper team has accomplished in this release:

  • We’ve added parameter name hints right to the code editor. This helps make C# and VB.NET code more readable.
  • Early support for Visual Studio 2019 Preview 1.
  • The code formatter can now detect the code formatting style right from your code and adjust the formatter settings accordingly (ReSharper | Edit | Detect formatting settings). No more looking through ReSharper formatter settings and configuring them manually.
  • ReSharper can autodetect the naming style you use in your code. No manual configuring of naming styles anymore to match the naming convention you use.
  • Improved C# 7 deconstruction support includes new/updated inspections and quick-fixes.
  • VB.NET 15.3 and 15.5 language support.
  • TypeScript 3.0 support.
  • Initial support is available for the new localization procedure in the latest ASP.NET Core projects. Most of the localization inspections, refactorings, and quick-fixes that you are familiar with from the old localization procedure are available.
  • Lots of new inspections, quick-fixes, and context actions have been added to C# code analysis for different cases.
  • A few performance optimizations have been made.
  • We’ve implemented the Introduce parameter refactoring for local functions.
  • A couple of new keys to run ReSharper Command Line Tools.
  • We’ve made ReSharper more FIPS-compliant by stopping the use of the md5 hash algorithm and eliminating all its previous uses in the codebase.
  • The Go To Action popup allows looking for Options pages.

You are welcome to check the What’s new in ReSharper page to learn more about the features and improvements in ReSharper 2018.3. See also the full list of requests we’ve addressed this release cycle.

As usual, all other ReSharper Ultimate tools get an update in this release as well:

  • ReSharper C++ 2018.3 – every bit better! Cleverer refactorings, new context actions, an even smarter Go to Declaration and Search Everywhere, auto-detection of code formatting settings and C++ naming schemes, and better error diagnostics on templated code. Besides all this, the release has improved C++/CLI support. If you are working with the Unreal Engine, you can find enhanced performance and parsing improvements made to the reflection macros.
  • dotCover 2018.3: In addition to multiple bug fixes, we’ve reworked the way coverage filters are organized. Now, there are two groups of filters in the dotCover options: runtime filters (those applied during a coverage session) and results filters (those applied to coverage results). The latter is extended with a filename filter. Use it to exclude unnecessary files from the results (such as auto-generated ones) and reduce “noise” in the coverage tree.
  • The biggest thing about dotTrace 2018.3 is the integration into JetBrains Rider. You can configure and run profiling sessions, get snapshots, and analyze them in the built-in viewer. Note that currently, the viewer cannot show a distribution of events on a timeline. That’s why timeline snapshots are opened as simple sampling snapshots.
  • dotMemory 2018.3 gets a new condition for taking a snapshot on the profiling controller: Get a snapshot if total memory usage exceeds X MB. You can also click on a timeline graph to get the exact memory data at a specific time point.
  • dotPeek 2018.3 supports decompiling more C# 7.x features and makes it possible to copy the fully qualified name (FQN) of a symbol to the clipboard.

Download ReSharper Ultimate

We’d love to hear your feedback on the ReSharper Ultimate 2018.3 release.

Comments below can no longer be edited.

19 Responses to ReSharper Ultimate 2018.3 is released!

  1. Avatar

    Jason Yu says:

    December 19, 2018

    It is unusable after update to 2018.3
    I throw incorrect error all over the place and cause a huge mess

  2. Avatar

    Developer says:

    December 19, 2018

    Just updated – forgot that you are breaking with every release :(. Time to re-think your extension architecture? Maybe use some decoupling?

  3. Avatar

    Kevin Gelking says:

    December 19, 2018

    Thank you very much for this update, I find the automatic display of parameter names extremely helpful. 🙂
    Thanks to this addition I no longer have to supply named parameters anymore for calls consisting of multiple bools, which improves first-glance-understanding a lot!

  4. Avatar

    Mark Wood says:

    December 19, 2018

    While I appreciate the new features, when are you going to focus on performance? I had to turn R# off today because my web project was so slow it was unusable.

    • Avatar

      Darren says:

      April 10, 2019

      Couldn’t agree more with this. I’ve literally arrived on this blog post seeking information on whether the latest release includes performance improvements and all we get is “A few performance optimizations have been made.”

      Sorry but the product is unusable now for me on a number of very well specced machines against moderately sized solutions so I won’t be resubscribing this year as the product spends more time disabled nowadays. Real shame as some of the features are outstanding.

  5. Avatar

    John B says:

    December 20, 2018

    I agree on the performance. It is terrible and so it should have first priority.
    ReSharper is no longer like sweets that you eat for enjoyment.
    It has become like bad-tasting medicine – you don’t eat it for enjoyment but because you need it.

    Also, I am simply unable to selectively disable the new parameter name feature.
    Unchecking “Automatically show parameter info in x milliseconds” simply has no effect

  6. Avatar

    E says:

    January 8, 2019

    2018.3 and 2018.3.1 are flat-out unusable. The performance is abysmal. VS 2017 now crawls so I’ve had to resort to downgrading to 2018.2.3.

  7. Avatar

    Alon says:

    January 24, 2019

    Rosyln support is completely boinked in VS19.
    It cannot distinguish C# from VB and causing VERY weird errors throughout the code (which compiled fine).

    Not usable for now unfortunately.

    • Alexander Kurakin

      Alexander Kurakin says:

      January 24, 2019

      @Alon, what do you mean by “Roslyn support”? Any additional details will be much appreciated.

      • Avatar

        Alon Fital says:

        January 27, 2019

        Hey Alexander,

        I’m working on project which use Rosyln for code analysis, ReSharper causes almost all Rosyln classes to show as red and recommends import using Microsoft.CodeAnalysis.VisualBasic (project is C#).

        Project compiles and works fine.
        Disabling R# makes all errors disappear and everything works great.

  8. Avatar

    Rick says:

    January 28, 2019

    Upgraded to 2018.3.1 and boom, the context action to insert XML comments is now gone.

    Why is it that every release changes some setting and somehow messes up everything already configured at the computer level?

    • Avatar

      Rick says:

      January 28, 2019

      I double-checked my extensions and upgrading ReSharper uninstalled “StyleCop by JetBrains” automatically. After reinstalling it the action to insert documentation was back.

      It might be good to have some kind of warning about which extensions are going to be uninstalled so we can reinstall new ones, or have the upgrade process take care of it automatically. I’ve been searching for hours on why this was not working anymore…

  9. Avatar

    Craig says:

    January 31, 2019

    Resharper 2018.3.1 doesn’t install (or it installs but is not active) into Visual Studio 2019 Preview 2. I have tried Repair, Uninstall-Reinstall but still nothing.

Discover more