Rider 2019.3 Early Access Program is Open!

Alexander Kurakin

Hello everyone,

Are you looking for something new to try in Rider to help you become a more productive developer? Then we have something great for you! We’ve just started the Early Access Program for Rider 2019.3!

RD2019.3EAP-blog@2x

In the first EAP build, you will find a highly requested feature in the debugger, lots of improvements in performance, initial support for MongoDB, and a timeline for GitHub Pull Requests. Sound intriguing yet? Let’s have a closer look at what we have in Rider 2019.3 EAP 1:

  • Rider 2019.3 automatically gets all the performance optimizations that we’ve added to the IntelliJ Platform during our recent Quality Marathon. To mention just a few key improvements: startup performance has improved a lot, smooth mouse scrolling is here, and we’ve eliminated all kinds of UI freezes. Read more about the performance improvements.
  • Docker-compose support has finally reached the debugger! We hope you enjoy it. In other debugger enhancements, “Pin to top” feature supports recursive evaluation, “Jump to Type Source” is now available, and the “Just my code” option for exception breakpoints works much better on Mono.

debugger@2x

  • Rider has added some initial support for MongoDB (read more). Other than that, we’ve extended Rider’s database support to the Oracle PL/SQL debugger, and added an easy way to google connection errors.
  • We’ve added a timeline for GitHub Pull Requests so you can observe all the relevant information about a pull request such as comments, reviews, and updates. In addition, to make Rider’s VCS support even better, we’ve improved the “Compare with Current” view, reworked the Clone dialog, and made it possible to push a non-active branch. Find more details in this blog post.

pull-requests-timeline

In addition to these four key areas we’ve improved, many more changes are worthy of note:

  • Improved C# 8 support including notnull constraint, the target-typed switch expressions, early support for default interface methods, a new hint "Local function can be static", and a new quick-fix "Add missing arms".
  • New Type Name Hints are available for lambda’s parameters, all var occurrences including pattern matching and tuples deconstruction, range variables inside LINQ statements, and at the end of a line in a method call chain.

type-name-hints

  • Now it’s possible to profile .NET Core applications on Linux and macOS using the embedded dotTrace plugin.
  • Web development: We’ve added support for the new syntax in TypeScript 3.7. Dart support is now available via a plugin, and there are lots of changes in Vue.js support. You can now see method return values in the debugger’s Variables view. Finally, we’ve improved memory usage when debugging with source maps.
  • Xamarin support has a couple of important fixes such as x:DataType and Class attribute support. Also, Now you can edit Android-specific project properties on the Project Properties.
  • Rider’s project model now extends any refactorings you make in your web language files, such as TypeScript files, to all your project files. For instance, “moving a TS class to a separate file” updates the corresponding .csproj file with the change. We’ve also improved the UX for the ”Not Built” project state in the Solution Explorer.
    Please note that we’ve dropped our support for .NET Core 1.* SDK as these versions have reached their End Of Support.
  • We now generate the predefined run configuration in a smarter way so that you can run it without any additional movements or adjustments. It also has an appropriate auto-generated name now, instead of the boring “Default”.
  • We’ve improved Rider’s support for project files (like .csproj files) by making code completion aware of various MSBuild things. You can also use an inspection and a quick-fix for <TargetFramework>/<TargetFrameworks> validation.

target-frameworks

One more thing: check out the new splash screen when Rider starts up. We hope you like it 🙂

Interested in fixed issues more than new features? Visit this page to see all the closed requests.

If you’re ready to download and try out this build, there are a few ways you can take part in this 2019.3 EAP:

We’d love to hear your feedback! Please add your comments below.

It’s worth mentioning that Rider EAP builds are free to use but expire within 30 days of the build date.

Comments below can no longer be edited.

17 Responses to Rider 2019.3 Early Access Program is Open!

  1. ‏‏‎ ‎ says:

    October 25, 2019

    “Type Name Hints” looks like a great feature.
    Also happy to see you guys are still improving performance.

    Thank you!

  2. Mart Leet says:

    October 26, 2019

    Azure plugin is must be. Sadly last eap period they created compatible version only for RC version.

    • Maarten Balliauw says:

      November 19, 2019

      Hi Mart, we just pushed a compatible 2019.3 version of the Azure Toolkit for Rider (EAP4).

  3. Dan says:

    October 27, 2019

    When I launch Sampling profiling on macOS, `Directory.GetCurrentDirectory()` is set to my User folder instead of the project’s root folder.

    • Konstantin says:

      October 28, 2019

      Thank you, we’ve reproduced this issue and will fix it soon.

  4. Leon says:

    October 27, 2019

    … visual studio community free and still better … including a scrollmap (https://youtrack.jetbrains.com/issue/IDEABKL-5794?_ga=2.129145674.773960058.1572192591-1328651985.1565983786 …9years what a joke jetbrains) MS did that right years ago along

    • feiti says:

      October 28, 2019

      If your most important feature for an IDE is really a scrollmap than obviously, you must be a very professional developer.

    • Nick says:

      October 28, 2019

      Visual Studio is a joke. It’s a cludgey, slow mess that Microsoft hasn’t properly maintained with bugs reaching all the way back to the 90s.

    • Marcel Bradea says:

      November 7, 2019

      There’s a much better version of this feature and it’s called Structure view.

      It’s not only a high-level view of your code – but contains code regions as well – which if you know how to properly incorporate into your codebase is an invaluable way of keeping your bird-eye/strategic and full-detail/tactical views always on hand as you code.

    • skotl says:

      November 15, 2019

      Don’t feed the troll, folks. If he’s been so besotted with VS for nine years then I find it hard to believe that he’s suddenly animated enough to be responding to EAP blogs about a scrollmap.
      In other news… we had a couple of diehard VS fans on the team and they switched to Rider when I showed them the embedded resharper hints. No going back for them now.

  5. jwh315 says:

    October 28, 2019

    First, thanks for implementing docker-compose debugging. I have been waiting for this feature for a long time and am really excited to use it.

    I am wondering if you guys have a blog post specifically on the usage of this feature. So far we have been able to get it working, but have had to make some pretty significant modifications to our Dockerfiles and docker-compose.yml specs to get it working.

    One of the main issues we are seeing is specifying an ENTRYPOINT in a Dockerfile causes the debugger to not get injected.

    • Kerry says:

      November 5, 2019

      I’m having similar issues when attempting to use docker-compose debugging. I was able to resolve some of the issues, but still haven’t resolved the entry point issue. Any pointers on how to get that one resolved would quickly move me from VS to Rider 🙂

  6. Jeb says:

    October 31, 2019

    Is is possible to configure a run config with just a .dcproj file or o you also need all related yml files ? I’m having issues running my compose project…

    • Sofia says:

      November 5, 2019

      Hi Jeb,
      This feature is not supported right now. Here is a ticket for watching and voting: https://youtrack.jetbrains.com/issue/RIDER-34861.

      We would be grateful if you described the issues you encounter with your compose project. You can directly file issues on https://youtrack.jetbrains.com/ and share Rider logs (Help | Compress Logs and Show in …).

      Thank you and kind regards,
      Sofia.

  7. Nuno says:

    November 8, 2019

    Hi all!
    I am a new Rider user and it’s good to see this software groving, however as I have posted in several places already, screenreader accessibility really could be improved!
    It’s a pity because Rider works much, much snappier than Visual Studio

  8. Scott says:

    November 22, 2019

    I love the idea of using t4 templates (EAP 5) for runtime file generation, but I’m stumbling over how to get this going. I had a look at the github page but there’s no instructions there.
    According to the Microsoft docs, if you were using this in Visual Studio then there would be a partial .cs file created – is that how it’s supposed to work in Rider?
    If so, how do we persuade Rider to generate that?
    Great work, as usual, by the way!

Subscribe

Subscribe to .NET Tools updates