AppCode
CLion
DataGrip
GoLand
IntelliJ IDEA
MPS
PhpStorm
PyCharm
Rider
RubyMine
WebStorm
Toolbox App
.NET Tools
ReSharper C++
Space
TeamCity
Upsource
YouTrack
Datalore
Hub
Kotlin
KtorReSharper Ultimate 2019.3 Release Is Out!
Hello everyone,
We’ve reached the last release milestone for this year – please give a warm welcome to ReSharper Ultimate 2019.3!
First, let’s take a brief look at the most important changes:
- The brand new Localization Manager helps you work more efficiently with many .resx files in your solution. It shows everything in your .resx files on a single grid, so you can observe the current state of the application or website localization and quickly find any missing resource values in any culture.
- C# 8 support has become even better and now includes support for
notnullconstraints, target-typedswitchexpressions, early support for default interface methods, and several new inspections and quick-fixes. - Code generation knows more about C# 8 and helps you learn it, too.
- Find dependent code now works for NuGet references and can be run for the whole solution instead of just a project.
By no means are these the only updates in this release. We have even more for you:
- C# naming settings now support reading from and exporting to EditorConfig.
- Type Name Hints are available for all var occurrences, lambda parameters, and more.
- The Unit Testing tool windows have new grouping modes and new filters.
- We’ve added more color settings for extra precision with code highlighting.
- ReSharper Command Line Tools are available on Linux and macOS, in addition to Windows.
This is just a short list of everything that has kept our team busy over the last 4 months. Please visit What’s New in ReSharper 2019.3 to read about all the changes in more detail.
Download ReSharper Ultimate 2019.3
ReSharper C++ 2019.3
ReSharper C++ 2019.3 is here to help you adopt C++20, including support for Concepts in Find Usages, the Rename refactoring, and code inspections. New type hints in the editor can make your code easier to read, while the new formatter options help tune your code style more precisely. There are also enhancements to navigation, live templates, and Clang-Tidy integration. For game developers working on Unreal Engine 4 projects, v2019.3 delivers more templates to generate UE4-specific code, as well as support for UE4’s Smart Pointers.
dotTrace 2019.3
dotTrace 2019.3 gets three new features:
- We have finally released the dotTrace command-line tool for Linux and macOS.
- Both dotTrace in Rider and the standalone dotTrace command-line profiler now support profiling .NET Core projects on Linux and macOS. Note that only projects targeting .NET Core 3.1 are fully supported. Because of .NET Core limitations, there may be issues with profiling projects that target .NET Core 3.0 or earlier, as in some cases the application being profiled may hang or crash.
- The call tree in the Timeline Viewer is now easier to analyze, thanks to the flame graph.
dotMemory 2019.3
dotMemory 2019.3 gets these updates:
- A new self-profiling API, which lets applications initialize and start a profiling session on their own. The self-profiling API is distributed as a NuGet package.
- The option to export instance details to a .json file (.bson, .hex, and .txt are also available).
- The ability to view the virtual memory address of an object instance.
dotCover 2019.3
dotCover 2019.3 gains support for Unity projects and projects using Microsoft Fakes. In addition, dotCover is now able to group coverage results by nested namespaces in Rider, in Visual Studio, and in reports generated by the dotCover console tool.
dotPeek 2019.3
dotPeek 2019.3 can navigate to the external sources of NuGet packages that have a source symbols package (.snupkg) and supports decompiling these additional C# 7 language features:
- Tuples
- Deconstruction
- Discards
Richard says:
December 11, 2019Intellisense / autocomplete is so badly broken in R# 2019.3 that I’m going to have to roll back to 2019.2.1, or disable R# altogether. Was this even tested?
Here’s hoping that 2019.3.1 fixes it; otherwise, we won’t be renewing next year.
Alexander Kurakin says:
December 11, 2019Hello Richard! I am sorry to hear you are experiencing such a weird issue in R# 2019.3. Do you have any R# plugins installed?
Richard says:
December 11, 2019I have previously installed some extensions. But as always happens, the upgrade obliterates them.
Rene Riedinger says:
December 11, 2019@Richard what do you mean with badly broken?
can you add more details?
Richard says:
December 11, 2019Wrong or no items selected in the auto-complete list;
Tab completion randomly inserting a tab instead of completing with the selected item;
Arrows sometimes moving to the next line of code, rather than selecting the next item from the auto-complete list;
Maria Pleskunina says:
December 13, 2019We already have a fix for the problem with navigating through the list of suggestions and, I hope, for the problem with tab. The fix will be available in 2019.3.1. So far, we’re discussing when to release it.
The good news is that there is a temporary workaround – you can try disabling the following option “Merge Visual Studio light bulb actions into ReSharper action indicator” in “ReSharper | Options | Environment | Editor | Visual Studio Features”.
By the way, is the problem with arrows the same as “Wrong or no items selected in the auto-complete list”?
Thank you!
Richard says:
December 13, 2019Disabling that option does seem to improve the behaviour. I’ll continue to use it this afternoon to see if keeps behaving.
The “wrong or no items” issue is an odd one. For example, I have a method in my base class:
Foo M()
In 2019.2, if I typed:
Foo x =
“M” would be the first item in the autocomplete list.
With 2019.3, “M” seems to be much further down the list, and appears after methods which return completely different types that aren’t assignable to Foo.
Maria Pleskunina says:
December 13, 2019Hmm, it’s interesting. Does the problem happen for a newly created solution? If not, it’s worth trying to clear caches via “ReSharper | Options | Environment | General | Clear caches” and check the problem once again.
Richard says:
December 16, 2019I’ve tried clearing the caches, and deleting the _ReSharper.Caches directory. It doesn’t make any difference.
Maria Pleskunina says:
December 18, 2019Richard, could you please attach R# settings (ReSharper | Manage Options | “Export to File” in the context menu for each layer) via “Submit a request” in https://resharper-support.jetbrains.com/hc/en-us for further investigation? Thanks in advance!
Nisse says:
December 11, 2019Where is the “enforce trailing comma” option?
Maria Pleskunina says:
December 13, 2019If I understood your question correctly, then this function hasn’t yet been implemented. There is a similar ticket: https://youtrack.jetbrains.com/issue/RSRP-452880.
Stanislav Perekrestov says:
December 11, 2019It seems Resharper 2019.3 sucks the whole life from my macbook.
Code cleanup doesn’t work.
CPU usage is 100% every time.
Rambalac says:
December 13, 2019Same for me. Cleanup does not fix any code style issues.
Funny that company whose main products are about fixing bugs has no idea about basic automated integration tests.
Maria Pleskunina says:
December 13, 2019@Rambalac, do you have a file header specified in “ReSharper | Options | Code Editing | File Header Text”?
Rambala says:
December 16, 2019I do have File Header text to follow stylecop
Maria Pleskunina says:
December 16, 2019@Rambala, sorry for the bad experience. We’ve already fixed this problem, the fix will be available in R# 2019.3.1 which we’re going to release this week.
As a workaround, please select all the contents of the file and run Code Cleanup.
Maria Pleskunina says:
December 13, 2019Sorry to hear you have some problems with the new version.
Could you please describe in more detail the problem with code cleanup?
Also, have you tried the following instructions: https://www.jetbrains.com/help/resharper/Speeding_Up_ReSharper.html?
Rambala says:
December 16, 2019That instructions do not help much. There is no any speedup even if everything is set to Fix silently.
The main issue Resharper freezes VS if there is JS code in the project. But even if js files are put to ignore it still kills VS. With 2019.3 update I had not uninstall it as I got tired to restart VS every 10 minutes. It freezes VS even if left doing nothing for some time.
Rambala says:
December 16, 2019* I had to uninstall
Maria Pleskunina says:
December 18, 2019@Rambala, sorry to hear that… If you decide to try ReSharper again, please let us know how it goes for you.
If performance problems happen again, we would be happy to take a look at the performance snapshot (https://resharper-support.jetbrains.com/hc/en-us/articles/207243205). But if VS freezes completely, it would be better to take a look at Capture Traces output (https://resharper-support.jetbrains.com/hc/en-us/articles/206546619-What-to-do-if-Visual-Studio-with-ReSharper-hangs-completely-).
Fabian says:
December 12, 2019As a performance suggestion, is it possible to suggest to use ‘Exclude From Project’ for the node_modules directory? In our big project this directory was freezing Visual Studio.
Filip says:
December 12, 2019Name Hints (inlay hints?) and especially it’s tooltip is unusable on environments with light UI and dark editor. It’s tooltip is using corectly “ToolTip-Background” color for background, but for text it is “CommandBarTextActive”. Result is dark color on dark background.
Maria Pleskunina says:
December 13, 2019@Filip, the following YouTrack ticket looks similar: https://youtrack.jetbrains.com/issue/RSRP-476448. Can you confirm?
Maria Pleskunina says:
December 16, 2019@Filip, sorry, the YouTrack ticket turned out to be about another problem.
We fixed the problem that you described earlier, the fix will be available in R# 2019.3.2.
David says:
December 12, 2019Syntax coloring is broken in the latest release (it does work in Rider). When I revert back to 2019.2.3 things work fine. When I upgrade to 2019.3 my syntax coloring (method names) are not honored.
David says:
January 7, 2020Ping – are you aware of this? 2019.3.1 still has the same issue.
David says:
January 8, 2020Filed issue RSRP-477653 [https://youtrack.jetbrains.com/issue/RSRP-477653]
Asia Rudenko says:
January 10, 2020Sorry for such delay with response!
David says:
December 12, 2019With the latest build 2019.3, the editor grays-out code after: Assert.IsTrue(await anAsyncTask). Is this a known issue?
Alexander Kurakin says:
December 13, 2019Hello David! Yes, we are aware of the issue https://youtrack.jetbrains.com/issue/RSRP-477423.
Liuhao says:
December 13, 2019R# 2019.2.3 and R# 2019.3 doesn’t work, I’m going to have to roll back to 2019.2.2. It’s OK.
Alexander Kurakin says:
December 13, 2019Hello Liuhao! Any details about what exactly does not work are much appreciated!
Liuhao says:
December 14, 20191. R # 2019.2.3 and R # 2019.3 versions click update to upgrade directly, and the display fails
2. After the local reinstallation, the smart prompt function cannot be used, and the auto-complete function cannot be used, such as coding any keyword will be programmed-> symbol, the method comment prompt cannot be completed
3. After rolling back to R # 2019.2.2 everything returns to normal, currently using 2019.2.2 version
Liuhao says:
December 14, 2019Installation environment VS2019 16.4 or VS201916.4.1
Alexander Kurakin says:
December 16, 2019Thanks for the reply! Could you please try disabling
ReSharper | Options | Environment | Editor | Visual Studio features | Merge VS light bulb action into ReSharper action indicatorand check the code completion issue once again?Liuhao says:
December 19, 2019I finally found that the function of R # 2019.3 is not unavailable, but it is slow to load. When the solution is opened, R # appears to be unusable. Without closing the solution, R # becomes available after a period of time; the same Under the configuration of R #, R # 2019.2.2 can be used soon under the same solution, so it feels that the 2019.3 version has lower initial loading performance than the 2019.2.2 version, and I hope to improve it in the R # 2019.3.1 version.
Martin says:
December 13, 2019“Type Name Hints are available for all var occurrences, lambda parameters, and more” i like this feature. Good job.
I don’t have any issues with ReSharper
Alexander Kurakin says:
December 16, 2019Thanks, Martin!
Michael Hartmann says:
December 16, 2019Error while trying to update JetBrains.ReSharper.SDK nuget package from 2019.2.3 to 2019.3:
Abhängigkeiten können nicht aufgelöst werden. “JetBrains.Profiler.SelfApi 1.0.0′ ist nicht mit ‘JetBrains.Platform.Core.Shell 193.0.20191207.64617 Einschränkung: JetBrains.Profiler.SelfApi (= 1.0.0-preview4)’ kompatibel.
Maria Pleskunina says:
December 17, 2019Hello Michael, the fix will be available in 2019.3.1. Sorry for the inconvenience!
Michael Hartmann says:
January 6, 2020Still not working with 2019.3.1 🙁
When trying to update JetBrains.ReSharper.SDK from 2019.2.3 to 2019.3.1 the error message now is:
Die Version von “JetBrains.NuGet.Core”, die mit ‘JetBrains.NuGet.Ultimate 5.2.0.20190806 Einschränkung: JetBrains.NuGet.Core (= 2.14.1.20190806)’ kompatibel ist, wurde nicht gefunden.
Maria Pleskunina says:
January 15, 2020Hello Michael,
Thanks for letting us know. I’ve submitted a new ticket: https://youtrack.jetbrains.com/issue/RSRP-477766. Please comment/vote for it to get the notifications about status changes.
Roland says:
December 19, 2019Performance of 2019.3 sucks. Same project, same machine as 2019.2.3 and its is WAAAAY slower. I am seeing “Resharper is thinking” all the time.
Tried profiling to submit issue, but it crashed and cannot be profiled :S
Anargyros Tomaras says:
December 19, 2019100% CPU………