Rider 2018.3 Is Just Around the Corner

As the title says, the Rider 2018.3 release is on its way. Before it hits us, take this opportunity to take all the new features and improvements for a spin!

The latest build, available here, includes:

  • Code Vision
  • Remote debugging via SSH
  • Rename Project refactoring
  • GitHub Pull Requests in the IDE
  • Zero-latency typing
  • Embedded tools for Android development
  • Integrated performance profiler on Windows
  • Assembly Explorer
  • Launch Settings
  • Type Hierarchy window
  • Enhanced language support for C# and VB.NET: improved C# 7 deconstructions, VB.NET 15.3 and 15.5, and more
  • Inline parameter name hints for C# and VB.NET
  • TypeScript 3.1 features, improved Angular support, several new intentions, and more
  • Newly redesigned Search Everywhere popup and Plugins pages in Settings
  • Enhanced F# support
  • Amazing capabilities for Unity

Download the latest Rider 2018.3 EAP build and try all of the above in action! We would appreciate hearing your feedback.

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

19 Responses to Rider 2018.3 Is Just Around the Corner

  1. Stuart Lang says:

    I’m currently building a Xamarin app in C# and F# on a mac, and Rider (EAP) is working so well for me right now, seriously impressed here. Loving the zero-latency typing. Great job all involved.

  2. Thomas says:

    I must’ve missed an EAP post, what is zero-latency typing?

    • Alexander Kurakin says:

      @Thomas, we haven’t published blog posts for EAP builds, everything about changes in EAP with some details can be found on the EAP page. In case, you are looking for a short explanation what is the zero-latency typing, so, here it is:

      Even for smart typing assists which do long tasks like reformatting code, Rider’s UI won’t be blocked and the code editor stays smooth and responsive. All asynchronous changes from Rider’s backend will be merged in a magical way later when they are complete.

  3. thoradrik says:

    What about .NET Core 2.2? Is new version of rider Rider going to support debugging for netcoreapp2.2 target?

    • Alexander Kurakin says:

      @thoradrik, .NET Core 2.2 support has not been planned for Rider 2018.3 release, so it is unlikely to happen before 2019.1 release cycle.

  4. Jeremy Morton says:

    Is commenting on a Pull Request planned for the future?

  5. Any idea when we can expect support for C# 8 / .Net Core 3.0 Preview?

    PS: Love the parameter hints introduced in the latest version. Makes codebases SO much more readable. Keep up the great work!

    • Alexander Kurakin says:

      @Marcel, definitely not in Rider 2018.3. We are going to look at it in 2019.1 release cycle.

      • Yup, understood from the 2.2 comment above that it’s not in scope for 2018.3. Was just wondering if Jan/Feb is realistic for a first EAP, or if we should prepare for later.

        Perfectly understand that no one would be holding you to any estimation of this. Cheers!

  6. Pingback: Dew Drop - December 10, 2018 (#2856) - Morning Dew

  7. Rasmus says:

    That sounds good. I’m particularly happy about “Zero-latency typing”: In Resharper we’ve been waiting for that for a decade or so. So I very much hope that you will apply your new understanding of how to do that to resharper in the near future.

  8. MH says:

    Any chance we can get some WebForms features in Rider.

    The only one I really need to help work with Legacy apps is when I add control (via code) to the page it adds a .designer.cs file.

    Unless it Rider can already do this?

  9. Lasse Vågsæther Karlsen says:

    Will we get 2018.3 in time for Christmas, so that we can wrap it an put it under the tree? :)

Leave a Reply

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