Dotnet logo

The .NET Tools Blog

Essential productivity kit for .NET developers


Rider 2018.3 is released!

Excellent news, everyone! We’ve just released Rider 2018.3 with lots of features you’ve been waiting for and all kinds of improvements to make coding easier still.

Rider 2018.3 is released

Let’s dive into this ocean of improvements and features:

  • Code Vision: try this new way of seeing useful information about your code right in the code editor. Usages, version control info, derived types, extension methods, and exposing APIs are now in plain sight, with no additional actions required!


  • Remote Debugging via SSH: need to debug an application on a remote machine? No problem, just call the action “Attach to Remote Process…” to attach to the process. .NET Full/Core, and Mono debuggers are supported.
  • Rename Project refactoring: no more manual renaming of all usages of a project. Call up this refactoring and you’ll be done before you know it.
  • Assembly Explorer now allows opening multiple assemblies, as well as traversing and exploring all open assemblies.


  • Zero-latency typing: even for smart typing assists that perform time-consuming tasks like reformatting code, Rider’s UI doesn’t get blocked and the editor stays smooth and responsive.
  • Launch Settings: support for launchSettings.json files is now available in ASP.NET Core projects.
  • We’ve redesigned the Search Everywhere popup and the Plugins pages in Settings.
  • Updated C# and VB.NET support includes improved C# 7 deconstruction support and language support for VB.NET 15.3 and 15.5.
  • An integrated performance profiler. Note that for now, the profiling features are only available on Windows.


  • Type Hierarchy tool window: explore the inheritance hierarchy of types via Navigate | Type Hierarchy.
  • Web development: from improved Angular support and better auto imports in JavaScript to debugging Node.js worker threads and support for TypeScript 3.1 features, and more.
  • VCS support: manage GitHub Pull Requests right in the IDE, and work with Git Submodules.
  • Android Development: lots of embedded tools and features from Android Studio are available, including a WYSIWYG designer, code completion for AXML/Android Manifest files, SDK/AVD Manager, and more.
  • Inline parameter name hints for C# and VB.NET are here.
  • Updated NuGet support offers Find this type on, a new quick-fix to Install missing .NET Core Adapter, and better and faster search in the NuGet window.
  • New language injections: SQL and other IntelliJ IDEA language injections now cover C# string literals.


  • Updated F# support; brand new F# lexers work for both IntelliJ IDEA’s frontend and ReSharper’s backend; Rename refactoring works for local symbols; and there are new grouping types in Find Usages.
  • Updated Database support delivers one more NoSQL database, Cassandra, and several improvements in SQL code completion.
  • Unity support updated: New inspections keep a tight watch on the performance of your Unity code; collect method and class usages from scene/prefab/asset files; Unity Explorer is now shown on Linux; and more!
  • Other features: there’s a brand new engine under the hood of the expression evaluator; Ctrl+Click on an entity declaration now shows the usages; the refactorings Move to Resource, Inline Resource, Move Resource, and Rename Resource are now available; you can now ‘Build only this project without dependencies‘; and, as we love saying, there’s even more!

Visit What’s new in Rider 2018.3 on the product website to find more details about these enhancements. To see the whole list of fixes in this release, check out the issue tracker page.

Download Rider

We’d love to hear your feedback on your experience with Rider 2018.3. Speak your mind we’re listening!

Comments below can no longer be edited.

28 Responses to Rider 2018.3 is released!

  1. KeepItReal says:

    December 18, 2018

    Thanks! 2019 is probably the year I switch from Visual Studio to Rider.

    • Developer says:

      December 19, 2018

      Given that ReSharper stopped getting new features and Visual Studio is catching up fast we might have an actuall choice of real IDE’s in future! I am leaning towards Microsoft since they own the stack I am using.

    • Mario says:

      December 19, 2018

      What I dislike about Rider is their horrible re-used UI of their other tools, it really depress me (/s). It clearly shows how Visual Studio has spent million of dollars on UX while Rider don’t, VS is super clean, way less clunky and with the help of, it looks fabulous. Rider on the other hand, feels like using Eclipse, which has to be the worst IDE ever existed.

      • Brad says:

        December 20, 2018

        Weird, Riders/IntelliJ overall aesthetic (navigation/context/UI) is one of the main reasons it was so easy to drop VS, VS for me is a nightmare for navigation, it’s just a classic Microsoft horrorscape of contextless garbage.

      • Oleg says:

        December 20, 2018

        What? Visual Studio is clean? It is really messy and over-bloated, while rider looks more lightweight.

      • Kim says:

        January 18, 2019

        What?? Do you mean VS Code?? Visual Studio is a clunky legacy third-rate IDE that was great in the C++ days, sucked in the .NET Framework era when we had zero choices, and now that .NET Core is in full flight, is irrelevant and probably actively harmful for the people still using it. Visual Studio users are bringing a pea-shooter to a fight where everyone else has tactical nukes. It’s so bad that MS saw fit to green light VS Code.

  2. Brad says:

    December 20, 2018

    Reading the full release notes, this sounds like a HUGE Rider update, can’t wait to test. 🙂

  3. Pawel says:

    December 20, 2018

    Sometimes, code completion seems to be broken. For example, when typing:

    A cursor is at “ben|” and IDE suggests to complete “ben” to “benchmark”. After hitting the enter key, the whole line is changed to:

    Restaring IDE helps.

    My version is:
    JetBrains Rider 2018.3
    Build #RD-183.5047.86, built on December 17, 2018

    JRE: 1.8.0_152-release-1343-b26 amd64
    JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
    Linux 4.4.0-98-generic

  4. Brad says:

    December 20, 2018

    Sigh, still no love for cg/shader completion/navigation in Unity? 2 years, cmon.

    • Maarten Balliauw says:

      December 21, 2018

      Hi Brad! Any chance you can make a request in our issue tracker for Unity support?

    • Developer says:

      December 21, 2018

      Unity is just an IoC container. Did you mean Unity3D?

      • Grigory Perepechko says:

        December 27, 2018

        Unity3D is now called Unity

  5. kong9011 says:

    December 21, 2018

    Yesterday I download and setup rider 2018.3, and trying to use it on my Unity Project.
    While I Comment few lines of codes , the file was saved,that trigger Unity refresh the Assets.
    I can not Find where is the setting for this issue…

    Is that a new feature in 2018.3?

    JetBrains Rider 2018.3
    Build #RD-183.5047.86, built on December 18, 2018

    • Mathijs Bakker says:

      December 26, 2018

      If you want to – for whatever reason – turn it off.
      Navigate to:
      Preferences/Languages & Frameworks/Unity Engine
      You’ll find the option under General

  6. Peter Bajusz says:

    December 21, 2018

    Indexing got really SLOW for Unity projects in Rider 2018.3.
    We have a project with 90 GB of assets and starting with this version Rider indexes ALL files.
    Also find references gets stuck from time to time looking into all the files…

    Had no issues like this with 2018.2

    • sbyzova says:

      December 24, 2018

      Please, try to disable a checkbox “Preferences | Languages & Frameworks | Unity Engine “[ ] Parse text based assets files for implicit script usages” and check if the problem persists.

      • Thomas says:

        January 18, 2019


        I have the same problem I think. Unity is saying “editor is compiling scripts”, and it takes a long time before I can deploy.

        Otherwise I’m loving it 🙂

  7. Alexandre says:

    December 22, 2018

    In contrast to 2018.2.3, version 2018.3 after the start of a large application in the debug freezes for 3-4 minutes.
    This was in one of the EAP.

  8. Robert says:

    December 24, 2018

    Today, i installed Rider 2018.3 but was not able to import the (exported) settings from Rider 2018.2.3. Rider 2018.3 shows a blank import screen – no components to select – noting.

    Any idea what’s going wrong here? Or is there another option to import my hard time configured settings?
    My maschine is a Mac.
    Thanks for some support.

  9. Yongyi says:

    December 26, 2018

    Find Usage in 2018.3 is significantly slower than 2018.2. Anyone feel the same?

  10. JepJep says:

    December 28, 2018

    Really great additions to an already amazing IDE! I absolutely love Rider, can’t imagine coding C# without it anymore.

    However It would be great if you could maybe somehow refine your release process in the way of continuous delivery. As a user I would like to get features faster via many small releases. For example maybe Code Vision could have been released individually? Releasing three times in a year is a bit scary from the user perspective as each release has so many new features there is almost certainly going to be handful of bad bugs. That’s why I’m a little hesitant to install new releases right away.

  11. Rider 2018.3 maintenant disponible ! | JetBrains France says:

    December 28, 2018

    […] Rider 2018.3 hits RTM a été publié pour la première fois sur le blog .NET […]

  12. Martin says:

    January 16, 2019

    I love rider since it’s first release. I test every release and I see a lot of new things and fixes in Rider 2018.3.1. Nice Work!!!
    Even though feels a lot heavier than 2018.2. My machine it’s low on resources so I will have to stay with previous version or Visual 2015 until I upgrade the hardware.

    • Martin says:

      January 16, 2019

      In fact… Memory usage opening the same solution on bothe 2018.[2|3] went from about 1.2 gb to almost 2gb. I have 8gb of ram and also need memory for other things…
      Memory readings are only taking care of rider64.exe and Jetbrains.ReSharper.host64.exe

  13. Kim says:

    January 18, 2019

    JetBrains, I love you guys, but 2018.3 is the most unstable release of Rider since the pre-GA days. It’s the first time I had to roll back to a previous release. Fortunately 2018.2 is solid. 2018.3 is feature packed (project renaming w/ namespace adjustment is insanely great), but Rider is mature enough now that stability is everything.

  14. Rider 2018.3の新機能 | JetBrains ブログ says:

    February 4, 2019

    […] [原文] Original post in English is written by Alexander Kurakin […]

Discover more