You asked us to support T4 text templates, and we’ve delivered! Based on our own generator and available as a pre-installed plugin, T4 templates support is here.
Now you can easily execute, process, and debug all your T4 templates in Rider. We hope you enjoy the new in-editor assistance, which includes:
includedirectives to make resolving C# code as correct as possible.
All these features work on Windows, macOS, and Linux.
Rider 2019.1 brought the performance profiler to macOS and Linux, but it only supported Mono and Unity Mono applications at the time. With this release, we’ve taken a huge step forward, and it’s now possible to profile .NET Core applications on Linux and macOS using the embedded dotTrace plugin. This means that you can profile any .NET applications on Windows, macOS, and Linux.
Note that only projects targeting .NET Core 3.1 are fully supported. Because of some .NET Core limitations, profiling of projects targeting .NET Core 3.0 or earlier may, in rare cases, cause the profiled application to hang or crash.
We really enjoy trying to improve the Unity scripting experience, and we strive to deliver something outstanding with every release. This time, we are introducing cross-platform test coverage and continuous testing for your Unity Edit mode tests!
These are some of the new features to get excited about:
UIElementswith syntax highlighting, code completion, and schema validation of UXML and USS files.
.asmdeffiles is back!
.metafiles up-to-date during refactorings.
These are just the highlights. As always, there are plenty of other smaller fixes and features in this release. Check out the full list in the changelog!
Rider 2019.3 automatically includes all the performance optimizations that we added to the IntelliJ Platform during our recent Quality Marathon. Here are just a few of the key improvements: startup performance has improved a lot, smooth mouse scrolling is here, and we’ve eliminated a lot of UI freezes. If you’re interested, you can read more about all the performance improvements on the IntelliJ IDEA blog.
In the 2018.2 release, we introduced Docker support into the debugger to let you debug
containers built from a
Dockerfile in Rider. However, debugging containers created
using Docker Compose (
docker-compose.yml) was not supported at the time.
Well, the wait is over! Docker Compose support has finally reached the debugger! Now you can debug multi-container Docker applications with the click of a mouse.
Edit & Continue can now apply changes to a running (not suspended) application,
and the application does not need to be stopped at a breakpoint. You can apply changes
anytime by clicking the “Apply Changes” link on the tooltip at the top of the
editor tab. Additionally, you can disable the automatic application of Edit &
Continue changes from the “Step”/”Resume”/”Jump
to Statement” actions by going to “
Settings | Build, Execution,
Deployment | Debugger | Editing during debug”.
Please note Edit & Continue is still only supported on Windows.
We have made lots of changes to other parts of the debugger. First of all, the Exceptions tree in the Breakpoints view has had a big update:
Secondly, Remote Debugging has received a couple of updates:
We’ve started experimenting with user interface and user experience improvements when working with version control systems like Git. In this release, a new live diff preview opens right in the code editor tab to provide a much better user experience.
We’ve also introduced a new Commit tool window, which is shown on the left by default so as to leave more vertical screen space for change lists, commit descriptions, and so on.
If you can’t find the Version Control tab on your first launch of Rider 2019.3, don’t worry; it’s still there, but it has a new name: Repository.
Besides that, we’ve improved the “Compare with Current” view, reworked the Clone dialog, and made it possible to push a non-active branch.
To learn more, check out the blog post A New Way to Commit! Introducing the Commit and Repository Tool Windows in Rider 2019.3.
In this release cycle, we’ve put a lot of effort into optimizing the AWS Toolkit plugin for .NET developers and making it compatible with Rider.
After installing the AWS Toolkit for Rider plugin, you’ll have everything you need to start working instantly with your AWS serverless applications.
We’ve continued to make Rider a great IDE for Xamarin development and delivered some sweet improvements for both Xamarin Android and Xamarin iOS:
Also, we haven’t forgotten about Xamarin Forms support, which has a couple of important
fixes such as
Class attribute support.
The new Rider release handles C# 8 even better. It now includes:
Additionally, the code inspection "Type or type member is never used" has been split into two separate options, one for types (Type is never used) and another for type members (Type member is never used).
The Generate action knows more about C# 8 and helps you learn, too, with:
Also, there is a new Option to use
System.HashCode to implement
GetHashCode when generating equality members or equality comparers for C# and
VB.NET, which will help make your code cleaner.
We hope you like the Parameter Name and Code Annotations hints we introduced in the Rider 2019.1 release. This release we go further and are ready to give you Type Name Hints. They are available for:
Most of us want to know where a particular reference is used in our code. For a long time, you could run the “Find dependent code” action on a reference to find all the places where types or type members from that reference appeared. However, there were some limitations. With this release, we eliminated a couple of them: Find dependent code works for NuGet references, and it can be run for a whole solution instead of just a project.
Now Rider definitely has more to offer:
In this release, we’ve delivered on one more long-awaited request. C# naming settings now support reading from/exporting to EditorConfig.
In addition to this huge change, there are several smaller changes that give you more control over the style of your code:
There is also a notification tooltip explaining the Configure formatting and Autodetect formatting features on the C# formatter options pages.
Rider’s project model now extends any refactorings you make in your web language files,
such as TypeScript files, to all your project files. For instance, “moving a TS
class to a separate file” updates the corresponding
with the change. We’ve also improved the UX for the “Not Built”
project state in the Solution Explorer.
Please note that we’ve dropped our support for .NET Core 1.* SDK, as these versions have reached their end-of-support dates.
Rider has added some initial support for MongoDB (read more). Additionally, we’ve extended Rider’s database support to the Oracle PL/SQL debugger and added new inspections and warnings, an inline query progress indicator, and an easy way to Google a connection error.
To learn more, check out the page What’s New in DataGrip 2019.3.
As usual, there are a lot of goodies for web developers:
To learn more, check out What’s New in WebStorm 2019.3.
Settings | Version Control | TFVCand turn it ON. This provides a dramatic speed improvement for the "Checking for changes" action (it’s now about 100~1000 times as fast in our tests). Many operations, such as Commit and History actions, will be ported to the new client after the initial release.
Free 30-day trial