Rider 2020.1 Roadmap

We’d like to share our plans for Rider 2020.1 with you and find out what we can do next to improve your development experience. Your feedback is always welcome!

For the 2020 release, we’ve been burning through the Great Ticket Close-out! We have been fixing bugs and implementing features that are important to make your experience using Rider the very best it can be.

We’re doing our best to target version 2020.1 to ship all these great features, but some require a lot of work and could ship in a later version. Here’s our top priorities for 2020.1:

  • Pencils – The new Pencils feature allows a user to change editor’s severity easily. Although Rider has so many excellent and popular intention actions and help, some users prefer a quieter experience. With just one click from a non-modal popup, you can turn on or off Code Vision, Parameter Hints, Unity Performance Hints, Errors, Warnings, Suggestions, Context actions, and many more.
  • Unity – XML documentation support for BCLs on Mono, new breakpoints which will suspend the Unity Editor, and support for shaders.
  • RESX – We have first introduced the RESX editor in Resharper 2019.3, but now this much needed feature is coming to Rider!
  • Blazor – Blazor is a blazing through the .NET space, and has become quite popular very quickly. So we’re working on improving Blazor support in our IDE.
  • UX – There’s a cleaner experience when using Threads View in Debugger

We are working hard on porting our backend to .NET Core. Although we are not targeting this to be the default in 2020.1, you will be able to try it out with an experimental flag very soon.

In addition to the features we’ve just mentioned, you can expect much better TFS support, along with hot reload for Xamarin, and all the goodies that will be available in IntelliJ IDEA 2020.1 and ReSharper 2020.1.

We’ve made some performance improvements in Rider 2019.3, especially around application startup. This time we are focusing on something a bit more narrow in scope – the project’s startup time. Prepare for blazing fast startups in the future!

What do you think about these plans? Feel free to submit a new feature request in our issue tracker if we’ve missed something, or upvote any existing requests to let us know it is important to you. We are looking forward to your feedback!

About Rachel Appel

Rachel Appel is a Developer Advocate at JetBrains focusing on .NET, Azure, and web development technologies. She has been in the business of creating software for nearly 30 years as an author, mentor, and speaker at top industry conferences around the world. Her hobbies include science, reading, languages, and travel. Follow Rachel on Twitter or check out her personal blog
This entry was posted in How-To's and tagged , , , , , , . Bookmark the permalink.

42 Responses to Rider 2020.1 Roadmap

  1. Tiago C Oliveira says:

    Hi Rachel, better filtering for the dotCover plugin was promised for 2019.3, was it moved to a future release?

    • Rachel Appel says:

      Hello Tiago, it’s planned for 2020.1 so stay tuned, it will be here soon!

    • Jan van Veldhuizen says:

      Yes, I hope DotCover will be avialable without the need of purchasing entire Resharper.

      • Alexander Kurakin says:

        Hello Jan! You don’t have to buy a separate ReSharper Ultimate license, you just need to upgrade your Rider license to “ReSharper Ultimate + Rider” pack. This upgrade is much cheaper than purchasing an additional ReSharper Ultimate license.

  2. Rasih CAGLAYAN says:

    Hi.

    Is there any plan for profiling improvements features ?

    • Alexander Kurakin says:

      Hello Rasih! What improvements do you expect to see?

      • Rasih says:

        Hi,

        For example

        – in asp.net core web development scenario
        – it is nice idea to see request details as spans
        – ef core – db query execution count and time for each
        – http requests and time details for each
        – full request execution time
        – execution time by method …

        As a summary it is nice idea to have features for improving performance via profiling each request.

        Also there is no profiling options available in macOS; i use asp.net core 3.1 but sampling is not selectable option for profiling.

  3. Julian Moschüring says:

    What does ‘Support for shaders’ entail?

  4. Keith says:

    It’s cool that you are adding all the fringe areas that visual studio support, but it would be nice to see some more core stuff, like an improved nuget package manager. I think a lot of innovations can be done there to make it easier to work with.

  5. Martin Odhelius says:

    “We are working hard on porting our backend to .NET Core. “. What exactly does that mean? Can you please explain a bit more? What kind of effects will this have?

    • Rachel Appel says:

      Some of the engine is written in .NET, and we’re porting it to .NET core, so it’s not the UX/UI, it’s the parts of Rider that you don’t necessarily see. This should manifest in greater performance as well as cross platform optimizations.

  6. Pavel Simsa says:

    Hi Rachel,
    (when) can we expect Rider 2020 EAP? 😉
    Thanks!

  7. Simon Vane says:

    The ONLY feature I care about is dramatically improving performance in Visual Studio (2019 latest).

    I have following all of your performance improvement advice but despite this I have had to stop using R# completely.

    I am using a Dell 5520 (i7, 32Gb RAM, M2 drive) and R# is simply unusable. It’s very frustrating not being able to use software I have paid for.

  8. Carel Lotz says:

    Immediate Window feature please – it only has 250+ votes :-)
    https://youtrack.jetbrains.com/issue/RIDER-2993

  9. Alexander says:

    Hi Rachel!

    Will we see Collaborative development in this version?

  10. trydis says:

    “We are working hard on porting our backend to .NET Core.”

    Really looking forward to trying this. It’s a resource hog now, running on Mono (macOS).

  11. Nirajkumar Bhatt says:

    Pin tab doesn’t actually freeze the tab like Visual Studio.

  12. Jack Ivy says:

    Jumping onto the sentiment that Keith expressed, while I understand the need to push for new features and ‘cool stuff’, I think there are plenty of quality-of-life improvements that would go a long way toward making Rider feel worth it. For example, all the weird issues caused by adopting the WebStorm engine including this one https://youtrack.jetbrains.com/issue/RIDER-30131

    As an aside, my entire team (10+) was burned pretty bad by the infinitely refreshing SVN commit window debacle that I reported at the very beginning of the 2019.3 EAP (October 31 to be exact), and it eventually became a critical IDEA ticket (https://youtrack.jetbrains.com/issue/IDEA-226333), which only makes me more frustrated that it wasn’t seen as a serious problem sooner. That fix finally landed in Rider 2019.3.3 a few days ago….

    Here’s to hoping this EAP will be more about (in this order):
    1. Not breaking things that already work, only to fix them months later
    2. Fixing existing bugs
    3. New stuff

    • Rachel Appel says:

      Jack,

      We’ve completed about 200 bug fixes for the EAP, compared to just the few “cool stuff” issues you see in this post. There are many teams and moving parts that need to align to address issues that originate in relation to the WebStorm engine. We are aware of the issue but don’t have an ETA for that particular issue’s fix yet.

      Please review the EAP guidelines here: https://www.jetbrains.com/rider/nextversion as they state “You expressly acknowledge that this version of the product may not be reliable, may not work as intended and may contain errors. Any use of the EAP product is at your own risk.” I suggest using stable versions for production/actual product development for entire teams. Our EAPs are specifically for testing out new features (that “cool stuff” you’re talking about). We suggest using stable versions so as to avoid the type of issue you describe on your team.

      Of course, we try not to break things (at any time) but there’s not a software team on earth that doesn’t have the occasionally break. When it happens, we fix as soon as we can.

      Our priorities for 2020.1 have been set and are as already outlined in this blog post.

  13. Uwe says:

    Any plans on making a decent, flexible window docking system like in Visual Studio?

    The Rider/IDEA system is very limited, compared to Visual Studio, unfortunately.

  14. Payam says:

    An environment to do C# or F# scripting in Rider similar to LinqPad would be much needed. I don’t know if such capability already exist, but I very much would love to have this capability.

  15. Looking forward to resx support. Having to fire up VS (and a Parallels VM before that!) only to edit a couple resource files doesn’t really make for a great developer experience :-)

  16. Dale E Strickler says:

    What about diagrams? class, project dependency, others? Diagraming seems like a major lacking right now and your other tools have some pretty good ones. Are they that hard to port?

    • Rachel Appel says:

      Hello Dale,
      We have some diagraming capabilities, such as the PlantUML plugin for class diagrams. For dependency diagrams, check out the Johnnyzzz or Dependency Analytics plugins, as well as some others. You can see the plugins under the Plugins node in the Preferences/Settings.

  17. David says:

    I agree with the general sentiment here, please focus on improving every day usage and quality. Coming from Visual Studio a lot of little things feel a little off in Rider, like intellisense for example.

    Thanks for the great work you are doing.

  18. Lázár Zsolt says:

    Hi! Is the Avalonia support being worked on? There is a pretty up-voted issue for it on Rider’s YouTrack (RIDER-39247). And if it gets implemented, Rider will leave Visual Studio and WPF in the dust, since Avalonia is cross-platform. I’m really looking forward for Avalonia support.

    • Rachel Appel says:

      Lázár,

      It won’t be in 2020.1, and we aren’t targeting any specific releases to support Avalonia at the moment. Check the issue (RIDER-39247) after the 2020.1 release, or in future roadmap posts to see if it’s been updated at that point.

Leave a Reply

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