Rider 2017.3 Early Access Program is open

Posted on by Alexander Kurakin

We have just started up another Rider pre-release cycle: please feel free to download Rider 2017.3 EAP!

Rider 2017.3 Early Access Program is open

The first EAP build contains the following new features and bugfixes:

  • New project templates.
  • Heaps of UI improvements in the Unit Tests window.
  • Many debugger enhancements such as Smart Step Into, async causality chain tracking, and support for dynamic modules/assemblies.
  • Performance improvements on loading and reloading solutions.
  • C# Interactive window.
  • Support for package references in classic .csproj projects.
  • Changes in settings: Export/import file, Reset and Copy settings to actions; Null Checking tab in C# code style settings; per-language separation on Inspection Severity configuration page.
  • Web.config transforms (XDT transforms).
  • Lots of improvements to support Unity.
  • Auto-open the namespaces during completion in F#.
  • Initial support for Value Tuples in VB.NET.
  • Updated code formatter, including new formatting options and fixes, notably for C# and HTML, as well as control of formatting settings via file masks from .editorconfig and via comments.
  • Improved Razor support.
  • C# 7 support extended with a code generation action that creates deconstructors from selected fields or properties.
  • New typing assists for multi-line comments and chained method calls in C#.
  • A fix for External Annotations support in .NET Core and .NET Standard projects.

Here’s the full list of fixed issues.

Come and download Rider 2017.3 EAP, or get it via Toolbox App.

Comments below can no longer be edited.

14 Responses to Rider 2017.3 Early Access Program is open

  1. Marcel Bradea says:

    November 24, 2017

    Which project templates have been added/updated?

  2. User says:

    November 25, 2017

    This EAP seems to be removing some keymaps, most notably the netbeans one. Is that intentional? Is there a workaround?

  3. NN says:

    November 25, 2017

    Are there any plans to fix TypeScript support bugs like https://youtrack.jetbrains.com/issue/RSRP-465302 and others ?

    • Alexander Kurakin says:

      November 27, 2017

      Are you experiencing this issue in Rider too, not only in ReSharper? Rider uses WebStorm engine to work with TypeScript, so that shouldn’t be relevant for Rider.

  4. Mark says:

    November 27, 2017

    I’ve noticed there’s a Run x with coverage… button appearing on the toolbar, but disabled. Sign of things to come?

    • Alexander Kurakin says:

      November 28, 2017

      “Run X with coverage” comes from WebStorm and mostly applicable for Jasmine tests using Karma framework.

      • Stelios says:

        December 5, 2017

        Hello Alexander,

        Hang on a second because I think I don’t understand: how does WebStorm is connected with the ability to run unit tests with code coverage? I came to ask the same thing, when will code coverage be available. And now I read this comment and I am more confused.

        • Alexander Kurakin says:

          December 25, 2017

          Sorry for the delay in replying you. All javascript support in Rider comes from WebStorm. WebStorm supports running karma tests with coverage https://www.jetbrains.com/help/webstorm/karma.html#ws_karma_code_coverage. The icon you see next to “Run/Debug tests” ones is a part of the WebStorm integration. Unfortunately, the icon exists even if your tests have nothing related to JavaScript.

  5. Dylan van der Merwe says:

    November 30, 2017

    When will we be able to do WebDeploy publishing through Rider?

    • Kirill Skrygan says:

      November 30, 2017

      Hi!
      We are planning to do this for the 2018.1 release.

  6. Ben Holtzman says:

    December 1, 2017

    Is there or will there be some kind of Visual Studio designer equivalent in Rider?

Subscribe

Subscribe to .NET Tools updates