Rider 2017.2 EAP build 3

We’ve got another fresh EAP build for you: get Rider 2017.2 EAP 3!

Rider 2017.2 EAP - build 3 - Early Access Program

Here’s the list of this build’s highlights:

  • Better npm integration: Rider opens the npm tool window and offers to run npm install on opening a solution that contains a top-level package.json file.
  • tsconfig.json is now detected and taken into account when analyzing TypeScript files.
  • Call Tracking and Value Tracking actions are now directly available from the Alt+Enter menu on member and parameter declarations.
  • Import and export of all global settings is available, including both settings coming from ReSharper and the IntelliJ platform.
  • Solution-wide analysis (SWEA) is automatically paused during NuGet restore.
  • Improved Unity support, including better highlighting in .cginc files and injected Cg fragments in .shader files.
  • Better presentation of paths to MSBuild, Mono and .NET Core in Rider settings (Build, Execution, Deployment | Toolset and Build).
  • Performance stabilization (in progress).

If you want to glance through the list of bugs fixed, here’s the list for you.

Please download Rider 2017.2 EAP 3 and give the new build a try!

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

7 Responses to Rider 2017.2 EAP build 3

  1. Derek Price says:

    Did you miss incrementing the EAP number in the title bar and Help | About? This is what I have installed:

    Rider 2017.2 EAP
    Build #RD-172.4144.808, built on September 29, 2017
    Rider EAP User
    Expiration date: October 29, 2017
    JRE: 1.8.0_152-release-915-b11 amd64
    JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
    Windows 10 10.0

    • Jura Gorohovsky says:

      We didn’t. We’re not using “build 3” anywhere inside Rider, 3 is just a serial number for the purposes of the EAP page and communications. The internal number of the build is #RD-172.4144.808, and it’s right in the build info you’ve provided. It’s not too useful in terms of communications though.

  2. Kostya Stankevych says:

    Any plans on implementing code auto-arrangement feature for C#? Love frequent updates and the way Rider is going, but really miss that feature.

  3. Matthew Brookson says:

    Can we expect to see the Package Manager Console similar to Visual Studio for .NET Framework in an upcoming release? This is the one thing that stops me using Rider on a daily basis as I work with EF migrations

Leave a Reply

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