Rider 2017.2 EAP 2: open folder, call and value tracking, and more

Rider 2017.2 EAP - build 2 - Early Access Program

Here’s a fresh Rider 2017.2 EAP build for you!

This build updates Rider’s front-end to IntelliJ platform 2017.2, with version control improvements, updates to JavaScript and TypeScript support, and a more native Windows 10 look and feel.

We’ve also worked on the project model, and as a result, Rider now lets you open individual files and folders, as well as attach folders to solutions. We made improvements when generating and inspecting code, added the highly requested call and value tracking from ReSharper, streamlined the way you change C# language level in your projects, enabled auto-starting and debugging the browser when running web applications, improved F# and Unity support, added (initial) support for lambda expressions in debugger watches, and fixed a number of bugs.

We’ll post more about the highlights of this new EAP build next week; meanwhile, please download Rider 2017.2 EAP and give the new build a try!

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

4 Responses to Rider 2017.2 EAP 2: open folder, call and value tracking, and more

  1. Stefan says:

    It seems that code analysis is broke in a kind.
    When I use public methods in a class for library projects, it always says that the method can be made private… Also protected methods in an abstract class are marked as “can be made private”

    • Maarten Balliauw says:

      Probably because in the library project, these methods don’t have any callers? Or do they? (in the same solution)

  2. Iain says:

    Rider is great for someone like me who doesn’t have a windows dev background as it means I can work with VS2017 developers on .Net Core 2.0 DevOps pipelines without having to commit a new IDE’s way of doing things to muscle memory. Rider is just like all my other Jetbrains IDE’s.

    Enjoying the pace of change, well done.

    Would be good to see Resharper command line tools be able to work in a sole .Net Core 2.0 environment as well so Teamcity + Upsource can have the same inspections results as Rider / VS2017 + Resharper in a .Net Core 2.0 setup.

Leave a Reply

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