ReSharper Ultimate 2019.2 Starts its Early Access Program

Today we are launching the Early Access Program for ReSharper Ultimate 2019.2.

ReSharper Ultimate 2019.2 EAP

Let me highlight briefly the key changes and improvements you can already try out in this first build of the ReSharper 2019.2 EAP:

  • There is initial support for the “Per-Monitor DPI Awareness” mode in Visual Studio 2019. If you disabled Optimize rendering for screens with different pixel densities via Tools | Options | Environment | General because of the rendering issue we had with the ReSharper tool windows, please enable it again and check out how it now looks.
  • We’ve updated the Performance Guide page. It has a new Windows Defender section and descriptions for all performance tips, which describe what exactly will be done after a suggestion is applied.
  • You can search in a file right through the Go to File member dialog.

Find in Files in Go to File Member

  • A new filter in the Go To Text results window to filter out comment lines.
  • The Advanced symbols options dialog under ReSharper | Options | Tools | External Sources now supports relative paths.
  • The debugger data tips respect the Enable property evaluation and other implicit function calls setting, and can evaluate property values on demand.
  • A new tooltip with the description of a keyword is available in the IL Viewer.

The full list of fixes that made it into this first EAP is on our YouTrack.

At the same time, ReSharper C++ 2019.2 EAP comes with a lot of new features and improvements:

  • Improved hints in the code editor. ReSharper C++ adds two new types of hints: hints after preprocessor directives and hints for function arguments passed by a non-const reference. Hints in aggregate initialization expressions now show the names of initialized base classes.

Hints in C++

  • New inspections and quick-fixes:
    • Several new inspections are available: “Unmatched preprocessor directive”, “Explicitly defaulted special member function is implicitly deleted”, and “Redundant final function specifier in a final class”.
    • “Use static_cast fix” for the “C-style cast used” inspection can be run in bulk and as a part of Code Cleanup.
  • Several updates in Navigation:
    • Go to declaration can navigate to the default constructor called when an object is default-initialized in variable declarations and new expressions.
    • Find usages finds usages of default constructors in default initialization.
    • Go to symbol now hides symbols with qualified names (e.g. out-of-class function definitions). When an item is selected, Go to symbol jumps to its definition, similar to how Go to declaration does.
  • More C++ 20 features are supported: conditional explicit, char8_t, pack expansion in lambda init-capture, default constructible and assignable stateless lambdas, C++20 rules for aggregates, consteval and constinit specifiers, C++20 improvements to structured binding declarations.
  • Code completion: The summary tooltip in the code completion popup is now colored and shows documentation for the selected item.

Summary tooltip in the code completion

  • Improvements to typing assist in multi-line comments: multi-line comments that use single-line syntax are automatically extended; extending multi-line comments now inserts correct indentation when virtual space is enabled.
  • Unreal Engine 4 support: The “Rename” and “Change Signature” refactorings handle RPC functions properly.

In addition to new features and improvements, ReSharper C++ has more than 70 bugs fixed in this first EAP build.

dotPeek 2019.2 EAP brings an unmanaged (win32) resources subtree in the Assembly Explorer and a couple of updates for the metadata tree: a description for unmanaged resources directories and entries (type, language) and a description for section’s headers.

Download ReSharper EAP

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

12 Responses to ReSharper Ultimate 2019.2 Starts its Early Access Program

  1. Jeff Chen says:

    When will you have more blog about performance and R# out of process ?

    It has been 6 month since you published last blog of performance series.
    https://blog.jetbrains.com/dotnet/2019/01/09/performance-improvements-resharper-2018-3/

    • Craig says:

      This.

      As a long time ReSharper user, it is sufficiently fully functional for my purposes (and I suspect most other user’s purposes) that I’d rather have the next 3 or 4 point releases of R# (i.e. 2019.x) introduce *nothing* new in the way of features and improvements and simply work on improving the performance.

      • Dustin Kingen says:

        I concur.

        ReSharper performance feels sluggish in Visual Studio 2019 with the long startup times and UI responsiveness lag.

        I work on several codebases through the day and when I open a new Visual Studio instance I feel like refilling my beverage or finding something else to fill the time.

        • MF says:

          It’s so infuriating when I’m trying to edit a file and everything suddenly decides to hang.
          Then VS says “Visual Studio stopped responding for 10 seconds. Disabling the extension JetBrains ReSharper Ultimate might help”.

          The performance degradation is almost to the point where I might try to learn how to navigate with virgin VS and ditch R# entirely.

    • Alexander Kurakin says:

      Hey Jeff! Sorry for being silent about the performance optimization for some time. Matt Ellis is working on a blog post which is going to reveal the current status of the “moving ReSharper out of process” story. I hope it will be published next week.

  2. Uwe says:

    Hopefully Blazor support for the latest .NET Core 3.0 (Preview 6+) is also improved, in terms of recognized directives like “@code” on the page.

  3. HamRusTal says:

    Please fix a grammar error: “check out how it now looks” — should be “check out how it looks now”.
    And a typo: “and new expressions..” — an extra period.

    • Alexander Kurakin says:

      Hello Ruslan! Thanks for catching the typo, I’ve fixed that! As for the grammar error, I’ve double-checked it a native speaker and “check out how it now looks” is totally fine.

  4. HamRusTal says:

    BTW when posting the previous comment I got “502 Bad Gateway” by nginx. Looks like something is wrong with the blog service.

Leave a Reply to MF Cancel reply

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