Early Access Program for Rider 2019.2 is Open!

Today we are happy to start the Rider 2019.2 EAP.


The first build has these goodies inside, which you can already try out:

    • ASP.NET: We’ve implemented our own “ASP.NET code-behind files” generator for aspx/ascx files.
    • Solution Explorer: “auto-scroll to source” is disabled for solution/project files, solution folders can now be renamed, and filtered solutions (*.slnf) introduced in Visual Studio 2019 can be opened in Rider.
    • dotTrace integration: All filters are available for Timeline Snapshots: Memory allocations, exceptions, and so on.


    • Type Hierarchy: Now there’s a button to show all external types in an opened hierarchy.
    • Build: We’ve added a system notification that tells you when the “Build Solution” action has been completed.
    • Unit Testing: Predefined options for the “Visual Studio path” field on the MSTest setting page under Build, Execution, Deployment | Unit Testing | MSTest.


  • NuGet: The package upgrading procedure has been improved. Support is available for xdt transformations, for a readme file, and for native credential providers discovered from %USERPROFILE%\.nuget\plugins.
  • Debugger: We’ve added a lot of performance improvements on stack calculation and stepping.

Besides that, we’ve fixed plenty of bugs. For the full list of these, see our YouTrack.

As usual, Unity support received yet another huge update:

    • We’ve decreased the memory and performance footprint of asset parsing. It means you don’t need to disable the Parse text-based asset files for script and event handler usages setting anymore to improve the performance.
    • New code vision metrics: to show the Unity Editor property value, and to show only asset usages (e.g. Game Scenes).


    • A new action, Find Usages in Unity, with a new “Navigate To” action for Unity usages.
    • A new action, Generate event function, available in a Unity type.
    • A new action, Show in Unity, in the notification panel inside .prefab and .unity files, which will focus the Unity Editor and preselect the corresponding prefab or scene file there.
    • Several new Live and File Templates.


  • A lot of other features and fixes as listed on the GitHub page.

There are several ways you can start participating in the 2019.2 EAP:

We’d love to hear your feedback!

PS: Starting from 2019.2 EAP, we have enabled sending the IDE usage statistics by default. This means that Rider will collect anonymous data about the IDE configuration and features/actions used. This will NOT include personal data or any sensitive information, such as source code or solution/project/file names. The data sent complies with the JetBrains Privacy Policy. You may disable this at any time under Preferences | Appearance & Behavior | System Settings | Data Sharing. Please note that this change affects EAP builds only. In stable releases, data sharing will still remain OFF by default.

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

41 Responses to Early Access Program for Rider 2019.2 is Open!

  1. Tom says:

    “We’ve decreased the performance” – I appreciate the honesty guys.

    • Alexander Kurakin says:

      @Tom, yeah, we are always honest. However, here we’ve decreased the performance footprint.

    • Bear says:

      “We’ve decreased the performance AND memory FOORPRINT of asset parsing”

    • Alexander Kurakin says:

      Anyway, good catch! I’ve updated the text a bit – “We’ve decreased the memory and performance footprint”

  2. Alexey says:

    Still no docker-compose debugging?

    • Alexander Kurakin says:

      @Alexey, unfortunately, still no docker-compose debugging in this release cycle. My apologies.

      • Kamil says:

        And what’s the timeline for this change?

      • Jacob says:

        Just want to add onto this comment thread to hopefully gain more exposure to this issue. As awesome as Rider is. Not being able to debug in a docker-compose environment basically makes it unusable.

        • Jacob C says:

          +1 to what Jacob says. I work for a dev shop with nearly 20 devs. We were hoping to see this in 2019.2.

      • Dmitriy Krasnikov says:

        You have been dangling this carrot for a very long time. I really couldn’t care less about new goto * features or imporvements to nuget, when I cannot use Rider in both of products we are having under development. All because we have multiple projects and microservices.

  3. P says:

    Any F# changes? What about code vision for F#? I was under the impression that it was targeted for Rider 2019.2

    • Eugene Auduchinok says:

      Yes, it’s targeted for 2019.2 but is not merged to EAP yet. EAP 1 includes few visible F# changes like version control provider for Code Vision, spell checker, and some subtle analysis and fixes. Most changes are infrastructure ones and are not directly visible. There’re more changes pending for future EAP builds and we will cover them together with already merged ones.

  4. John says:

    Are you seriously removing comments with honest questions here?

    • Alexander Kurakin says:

      Hello John! Please, could you share more details about removing comments? We’ve removed nothing for this blog post.

  5. No Sql Server Project Support jet? :'(

    • Alexander Kurakin says:

      Hey Alexander! Unfortunately, Sql Server Project Support has been postponed and won’t be delivered in Rider 2019.2 release.

  6. jay says:

    Will you include Net Core / Asp Net Core profiling on Linux/Unix ?

  7. Chris says:

    Is the out of process changes targeted for this release?

    If not – when?

  8. JF says:

    The link to the support system takes me to a page that does actually list any bugs:


  9. Andrii says:

    What happened with prepare for commit window?

    • Sandro says:

      It’s now under the Version Control Tab in the Toolbar per default but it can disabled in the settings under Version Control -> Commit Dialog -> Disable “Commit from the Local Changes..”

  10. Mykola Balakin says:

    Project files aren’t opened for edit on click in Solution Explorer anymore. Is it an intended behavior? Is there a setting return back previous behavior?

  11. Evan says:

    Is there any chances to see C++ api for custom mono/dotnet-core hosted applications? We’ve implemented custom profiler on top of mono api in our application (mono is used as scripting engine), but it is far from dotTrace’s functionality.

    • Alexey Totin says:

      Hi Evan,
      could you please clarify what API do you need? dotTrace is able to profile both Mono and .NET Core applications

      • Evan says:

        I need an ability to attach profiler to unmanaged C++ application which embeds mono through mono_profiler_load or your custom made API (like we have in C#). It would be really cool feature since all who use embedded mono (or dotnet-core hosting) has to implement own profilers with mono callbacks.

  12. Vukasin says:

    How to enable DevExpress controls?
    Is it possible to use DevExpress for wpf project?

  13. Vukasin says:

    Ok, to clarify my problem, I have a dll project, and in that project I want create wpf views, but when right click on project, there is no User control or Window, just Windows form.

Leave a Reply

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