Rider 2018.1 EAP is open

Good news, everyone! GREAT news everyone! Today is great because we are welcoming the Early Access Program for Rider 2018.1! Break down the walls to the future and give the first EAP build a try.

Rider 2018.1 Early Access Program

Let’s have a look at the new features and fixes inside:

  • Enjoy improved support for authenticating against private NuGet feeds. Rider automatically displays an authentication prompt when needed, and supports credential providers for popular NuGet hosting solutions such as MyGet and Visual Studio Team Services (VSTS).
  • We’ve added the ability to edit project properties in .NET Core solutions.
  • In the Debugger tool window, return value locals now contain text from the source code.
  • The application’s embedded console in the Debugger tool window displays output more reliably (on Windows).
  • We’ve added a new simplified way of exploring exception details – the Exception popup.
  • The debugger’s attach window displays the process username (on Windows) and suggests elevating permissions.
  • Rider shows the display text next to the project name if ProjectUISubcaption is specified in the project file.
  • Ideolog plugin for displaying, searching, sorting and filtering your .log files is available for download from the IDE: Preferences | Plugins | Install JetBrains plugins…

Starting with version 2018.1, we are working on ensuring a smooth connection between Rider and Unity Editor. This will bring about a set of great new features, and some of them are already available to try:

  • A new Unity logs tool window provides a handy way to explore the same logs from the Unity editor console with hyperlinked stack traces.
  • Feel at home with the Unity Explorer structure view of your solution, showing the same view of your assets as you see in Unity.
  • The Game View actions (Play/Pause/Step/Stop) are available directly from Rider.
  • Thanks to the two-way communication, any changes applied in Rider in Edit mode will be instantly delivered to the Unity Editor.
  • Code completion, find usages, and usage highlighting are available for ShaderLab properties when used in Shader blocks (not yet in Cg/HLSL blocks, but we’re working on it).
  • We’ve fixed ShaderLab color reference handling with non-US locales (thanks to our contributor!).
  • Rider now supports the BaseDirectory project property, which Unity projects use to focus the Solution Explorer on the Assets folder.

Note: To install the new version automatically, please manually remove the Unity3dRider.cs plugin from the IDE. Sorry for the inconvenience!

50+ issues were also fixed. Please see the full list for more details.

Grab the fresh Rider 2018.1 EAP build from our website, update via Toolbox App, or install it beside your stable Rider version.

Last but not least: we love hearing from you! Feel free to suggest a new feature or report a problem in any way that’s convenient for you: this blog post, the issue tracker, or Twitter.

P.S: Most of these features will be covered by detailed blog posts, so stay tuned to learn more.

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

42 Responses to Rider 2018.1 EAP is open

  1. Dylan says:

    The only thing really holding me back from using Rider more is the lack of publishing options like WebDeploy. Any news on when something like that will happen?

  2. David says:

    Hi !
    Can we hope a true profiling tools on linux edition ?

  3. Soheil Alizadeh says:

    Thanks rider, I hope that the EF support feature is cross-platform and I can us ef 6 migration on Linux or Mac OS.
    also I wait for good publishing tools for asp.net web sites.

  4. EAP means the early access programme. Rider 2018 is good for EAP. you can use this while developing any project. I read this article and found this is good for every person.

  5. Ty says:

    Had to uninstall after 20 seconds as all menu items were miniature. Maybe an issue with HDPI or font sizing, but a big issue for those with large monitors. Back to 2017.3 now and all ok.

  6. Chris says:

    Loving your commitment to supporting Unity! :)

  7. Mariusz says:

    It looks great, but what about Xamarin developers? :( There are only 2 fixes related to Xamarin. I’m still waiting for support editing XIB files from Rider…

    • Ekaterina Zharova says:


      We care about Xamarin developers too and will try to make your experience with Rider better in 2018.2.

  8. Alexey says:

    The feature we miss the most is debugging Docker containers. It has fix version 2018.1 in issue tracker, but it’s still not there.

  9. Lauri says:

    Could you please give any kind of an ETA for either some sort of continuous testing tool or dotCover support for Rider?

  10. Israel says:

    Any news about having the same Android UI Editor from the Android Studio to work for Xamarin projects (axml files)?

  11. Mateusz says:

    Great news! But (there is always some “but”)… I still wonder if remote debugging support (eg. via msvsmon) is doable this year.

  12. Fabricio says:

    Hi, I’m a Unity user and I simply LOVE what you are doing, But two things are annoying me.
    1. Every time Unity recompile Rider’s plugin logs “Rider plugin initialized …” with the logging level, but no matter what I set as my logging level it will always be shown.
    2. The Unity logs window does not clear or stacks logs as Unity does, the stacking feature I don’t really care, but not clearing automatically or option to make it possible (not the button to clear), really annoy me.

    • Ekaterina Zharova says:


      We appreciate your feedback, thank you!

      I created requests for these issues, feel free to follow and vote for them.

  13. Linkyu says:

    Hi, this issue https://youtrack.jetbrains.com/issue/RIDER-609 (XAML User Interface Designer for WPF) was eventually planned for 2017.3, then for 2018.1, but is not mentioned anywhere here.

    Is it postponed or is it still planned for the full release of 2018.1?

  14. George Cook says:

    where is the unity log tool window? I can’t find it; and can’t wait to try it out!!!

    • George Cook says:

      okay – I worked it out – it’s an icon at the bottom. Would love a shortcut key for that. Love it though – so much quicker than my current solution.


      • George Cook says:

        and further want to add to that – playmode/edit mode logging!? Is one of you guys over at Rider doing Unity dev on the side?! :) That was a genius touch – whoever thought of that feature needs a pat on the back.

        • Ekaterina Zharova says:


          thank you, we glad to hear it :)

          Could you please add the details, what exactly this shortcut key should do?

  15. Andreas says:

    Great work! When to expect the releases 2018.1 and 2018.2? Ant detailed roadmap to follow?

  16. Saxxon says:

    Excellent! Thank you all for the hard work you do. Will we be seeing any test code coverage features this time around?

  17. Miha Krajnc says:

    Maybe I’m doing something wrong but I can’t find any new features that are supposed to be Unity related, except the Unity Explorer window and a run configuration “Attach to Unity Editor & Play” :(

    Any idea why? My Unity version is 2017.3.1p1

    • Ekaterina Zharova says:


      I suppose it may be caused by this: to install the new version automatically, please manually remove the Unity3dRider.cs plugin from the IDE.

      Meanwhile, we already have a fresh EAP build, feel free to grab it from our website or update via Toolbox App.

    • Ivan Shakhov says:

      Miha, did updating to new eap https://www.jetbrains.com/rider/eap help?

      • Miha Krajnc says:

        Updating to the latest EAP worked! The new DLL got generated automatically, and I now get the Unity tab in the bottom right. Thanks! :)

        Just a note, I also updated unity to the latest beta (b10) in the mean time, not sure if that had any effect though.

Leave a Reply

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