Dotnet logo

The .NET Tools Blog

Essential productivity kit for .NET developers


Rider 2019.3 Release Is Out!

Hello everyone,

We published Rider 2019.3 just moments ago. Let’s walk through the key improvements in this update which the Rider team has focused on for the last four months.


Let’s highlight the most important features in this release:

  • Outstanding support for T4 templates is here with capabilities such as template execution, debugging, code highlighting, navigation, refactorings, code completion, and much more.


  • We’ve made a huge step forward in performance profiling, so now you can profile .NET Core applications on Windows, Linux, and macOS right in Rider.
  • If you are a Unity developer, you should benefit greatly from the cross-platform unit test coverage and continuous testing, which finally supports Unity tests!
  • Startup performance has been improved, smooth mouse scrolling is here, and a lot of UI freezes have been eliminated. These are just a few of the performance improvements in Rider 2019.3. (Note that this chart is not an accurate benchmark, but a quick indication of the change in startup time of Rider 2019.2.3 vs 2019.3)


  • Docker-compose support now covers the debugger. Enjoy debugging multi-container Docker applications with the click of a mouse.
  • In version control support, we’ve started experimenting with the user interface and user experience when working with version control systems like Git. Check out the new live diff preview, a new Commit tool window on the left-hand side of the IDE, and several other improvements.


If none of the above caught your interest, we have more new features for you still:

  • Edit & Continue can now apply changes to a running (not suspended) application, and the application does not need to be stopped at a breakpoint.
  • The debugger in general has many improvements. The Exceptions tree in the Breakpoints view is updated and Remote Debugging is enhanced, to mention just a few.
  • The AWS Toolkit plugin is now compatible with Rider! It supports creating, running, and debugging an AWS Lambda locally and remotely. Cloud Debugging support is also here.


  • Database support has several updates, with the biggest highlight being early MongoDB support.
  • C# 8 support becomes even better and includes support for notnull constraints, target-typed switch expressions, early support for default interface methods, and several new inspections and quick-fixes.
  • For Xamarin developers, we’ve got better discovery of Apple devices and simulators, a list of connected Apple devices on the toolbar, and a “Publish Android APK” action for Xamarin Android projects.


  • Find dependent code now works for NuGet references and can be run for a whole solution instead of just a project.
  • The Quick definition overlay tooltip is available for any symbols in the code editor


  • C# naming settings now support reading from / exporting to EditorConfig.
  • Support for TypeScript 3.7 is here alongside other improvements in support for JavaScript, TypeScript, Vue.js, and Angular.
  • Type Name Hints are available for all var occurrences, lambda’s parameters, and more.


  • Identifier highlighting has been completely reworked with a separate page for C#, separate colors for preprocessor directives, static methods, fields, etc.

There’s one last thing we’d like to mention, which is a small but very handy improvement for today’s .NET Core era. If you’ve ever added a second target framework to your .NET Core app by editing a .csproj file manually, did you forget to change TargetFramework to TargetFrameworks? I would venture a guess that you have, and probably more than once.

Rider to the rescue! We’ve added an inspection to warn you about this TargetFramework/TargetFrameworks problem and eliminate it with an appropriate quick-fix:


These are the key highlights out of all the cool things waiting for you in v2019.3. For more details, please visit the What’s New in Rider 2019.3 page.

We hope you enjoy this update. Try it and share your thoughts and impressions with us!

Download Rider 2019.3

Comments below can no longer be edited.

32 Responses to Rider 2019.3 Release Is Out!

  1. Tom says:

    December 11, 2019

    What’s the unit for vertical axis on performance chart?

    • Alexander Kurakin says:

      December 11, 2019

      Hello Tom! Seconds

  2. Lev says:

    December 11, 2019


    Your VCS tooling is freaking amazing! I was recently amused by an opportunity to work with several repos simultaneously. Very cool!
    Cannot get used to new VCS interface though. For me it was more convenient to work from one separate tab (or window in my case): show local changes, look though the log, push/pull and commit.

  3. Alex says:

    December 11, 2019

    Is it possible to disable opening “Repository Diff” tab? Sometimes it is more comfortable to open diff in new window on first display and watch to another opened file on second display. Now I need to close tab with diff to return to my opened file. It’s annoying.

  4. Mateusz says:

    December 11, 2019

    Is there AAB support for “Publish Android APK” action for Xamarin Android projects?

  5. Ivan Kashtanov says:

    December 11, 2019

    It seems to me that the update broke running executables accessible via PATH settings.

    Rider refused to build projects that require a dotnet command line tool.

    Rider terminal gives “not an executable” message for “node -v”, “git -v”, “dotnet -v” commands. Standard Windows cmd has no problems with them. PATH hasn’t changed, and the dirs that should be there for those commands to work seem correct.

    Rolling back to 2019.2.3 didn’t help though, now I have the same problems there. Didn’t have them before update.

    I guess I’ll have to go back to VS for some time.

    • Ivan Kashtanov says:

      December 11, 2019

      Found out the problem disappears after a few restarts (not including a start after update/rollback). In case of 2019.3 it took two restarts for console tools became visible in Rider terminal again.
      Still not sure what the problem was and if it’s gone for good.

  6. David says:

    December 11, 2019

    Have you fixed Blazor support???

    • Christian Andersen says:

      December 12, 2019

      It appears it has been pushed to 2019.3.1 according to youtrack.

  7. Mark says:

    December 12, 2019

    Try using T4 and get error: [Error] Fatal internal error

    Cannot resolve symbol ‘int’

    • Olga Varfolomeeva says:

      December 13, 2019

      Hello Mark,
      Could you please describe the issue in more detail? What’s the other content of the file?

      • Dmitry says:

        February 7, 2020

        You will get this error if you add the T4 template to the root of the solution (not in the project) and try to run it.

  8. Steve says:

    December 12, 2019

    I consider buying Rider for hobby projects. With Christmas and a new release coming:

    Will there be any discounts? or did I just miss them?

    Unfortunately I’m not a student to get a free licence…

    • Alexander Kurakin says:

      December 13, 2019

      Hello Steve! We have no plans to do any special Christmas discount. However, feel free to drop a line to our sales department about a discount Thanks!

  9. David says:

    December 12, 2019

    With the latest build 2019.3, the editor grays-out code after: Assert.IsTrue(await anAsyncTask). Is this a known issue?

  10. David says:

    December 12, 2019

    How do I configure Rider to run tests in parallel? I have a RunSettings file with:

    <!-- Auto-select based on number of cores available. -->

    Visual Studio test runner runs such tests in parallel but ReSharper/Rider test runner doesn’t. Is this a known issue?

    • David says:

      December 12, 2019

      Sorry the text didn’t appear right. The RunSettings are:


    • Alexander Kurakin says:

      December 13, 2019

      Hello David! Please file a support request here and attach the RunSettings file. Thanks!

  11. Dorel says:

    December 13, 2019

    I cannot find or update any nuget packages from the Nuget window.
    The search returns zero results for everything that I search.
    I didn’t change anything to my Sources.
    No thing gets logged in the Logs tab.
    Please help.

    • Alessio says:

      December 16, 2019

      I have the same issue since updating to 2019.3
      Rolling back to the previous one fixed it.

    • Alexander Kurakin says:

      December 16, 2019

      Hello Dorel! In case you experience this issue on Linux, then we are aware of such an issue Please, install the latest mono version. It should fix the problem with certificates that affects Rider.

  12. Zhen Zhi says:

    December 18, 2019

    Is there an issue with the SVN plugin? It is trying to refresh VCS history for very long time. This doesn’t happen in 2019.2.3.

  13. Gleb says:

    December 19, 2019

    Doesnt work with Unity.

    Tested in Unity 2019.2.17

    Tried to open old project in which I worked in Rider 2019.2.3 and couldnt get rid of 10000 of errors on everything, seems like the code isnt compiling.

    • Ivan says:

      December 19, 2019

      Make sure that new Rider version is selected in Unity as External Editor. You may delete sln/csproj files, then opening again from Unity would regenerate those files.
      If project compiles in Unity but is red in Rider for some unknown reason you may also try File-Invalidate caches and Restart.

  14. Nikita Tarasov says:

    December 19, 2019

    Is there the way to disable t4 template analysis? My templates doesn’t compatible with your engine because of using VS automation tools. Seems that is the reason I have huge performance issues with 2019.3 Rider now

    • Alexander Kurakin says:

      December 19, 2019

      Hello Nikita! Settings | Plugins | “Installed” tab | Type “ForTea” | Disable. Please let us know if it helps with the performance issues. Thanks!

      • Nikita Tarasov says:

        December 20, 2019

        Thank you, it helped. I had huge delays before tips appearance (method usages, implementations, suggests etc)

Discover more