What’s New in Rider

Rider is ready for Unreal Engine development on all three major platforms: Windows, Linux, and macOS. It works natively with the .uproject model, saving you time on intermediate project model generation.

The UnrealLink plugin enables advanced integration between Rider and Epic Games’ Unreal Editor. The plugin:

• Brings Blueprints information to the editor.
• Adds settings for managing game launch.
• Provides a more convenient version of the Unreal Editor log.

Rider is powered by ReSharper C++, which offers cutting-edge native support for modern C++. Benefit from its 1300+ code inspections, 290+ quick-fixes, solution-wide refactorings, and code generation abilities. Whether you’re working with the C++ code of your game, Unreal Engine code, or shaders, Rider helps you instantly navigate through it and explains it with inlay hints.

Learn more

Unreal Engine reflection macros and reflection specifiers are more than plain-text substitutions for Rider. Autocompletion and quick documentation are knowledgeable about these entities and help you code effectively. Similarly, Unreal Engine remote procedure calls are more than regular functions, and Rider matches them during code navigation and code generation.

Rider is integrated with UnrealHeaderTool and shows the same errors and warnings that you would normally see at compile time right in the editor while you are editing your code. The process has been optimized to have minimal impact on overall performance.

Rider detects Unreal Engine projects and automatically uses the Unreal Engine naming convention rules when generating and analyzing code in these projects.

The LLDB-based debugger with Unreal Engine Natvis support helps you dig up any issues in your game’s code or in the engine. You can set line, symbol, data, and conditional breakpoints. You can also step through the code, evaluate expressions, and even see the variable values right in the Rider editor during the debug session.

Rider comes with out-of-the-box support for the Unreal Engine Automation Testing framework. Launch tests from the Unit Test tool window or directly from the editor, review their results, and rerun failed, all, or specific tests.

Rider now supports a Beta version of our remote development workflow. It allows you to connect to a remote machine running Rider’s backend from anywhere in the world. All the processing happens on that powerful remote machine, and you can work on your project as seamlessly as if it were on your local machine. This functionality can be initiated from Rider’s Welcome screen or from a new application called JetBrains Gateway, which is available in the Toolbox App.

What’s more, you can create, prebuild, share, reproduce, hibernate, and manage dev environments with JetBrains Space – a unified platform for the entire software development pipeline. Check out this blog post for more details.

The new main toolbar looks incredible, and people love it. But there was no way to add custom widgets or rearrange existing ones, which many have complained about. You asked, and we delivered! You can now add new elements to both the left and right sides of the toolbar, as well as rearrange and remove widgets.

There are two ways to open the toolbar customization page:

• Preferences/Settings | Appearance & Behavior | Menus and Toolbars | Toolbar
• Right-click on the toolbar and select Customize Toolbar.

If you use the new main toolbar, which we released in Rider 2021.3, you have probably noticed that there is no way to start profiling with dotTrace right away. In this release, we addressed that inconvenience.

The Profile with Timeline, Profile with..., and Profile running process... options are now available in the Run/Debug widget’s More menu (the ‘kebab’ icon).

Fast mode has come to Docker and Docker-Compose solutions, which should significantly reduce build times during development!

Building your projects within a container can be significantly slower than building the same project on your local machine. With Fast mode enabled, Rider will first create the base stage of your Docker image using docker build, but then it will build the project on your host machine, which is significantly faster. Finally, the project artifacts are mounted to the Docker container as a volume. This mode is for Debug configurations only, and projects built under Release will be built using the steps found in your Dockerfile.

You can disable the Fast mode for any particular run configuration via Edit Run Configuration | Build | Modify options | Don’t use Docker fast debug.

Search Everywhere is the main entry point when you are looking for something in your solution, IDE settings, or Git history. Starting from Rider 2022.1, we’ve added the new Text tab, which shows all text occurrences in the solution that match the string while you are typing it. It runs full-text search through all code and text files, including .cs, .fs, .cshtml, .json, .js, .css, .editorconfig, .cvs, .dockerfile, .md, and .txt files.

As usual, all these results appear on the All tab as well.

However, you can narrow the scope of files where you want to run this search:

• By search area: All places, Recently viewed files, Local changes, or Data sources.
• By file type, with a predefined list of values or with manually specified file masks.

We’ve replaced the Event Log instanсe with a new Notifications tool window to more clearly highlight important and helpful notifications from the IDE. With this update, we aim to make notifications more visible and keep them better organized in a dedicated tool window that you can access from the navigation bar.

All notifications that appear in the Notifications tool window are sorted into two types: Suggestions and Timeline.

The Suggestions section presents notifications that are considered useful or helpful in most use cases. Additionally, Suggestions can be important or regular. If you get an important one, you’ll see a red circle on the bell icon on the navigation bar. Regular suggestions are indicated by a blue circle on the bell icon.

In the past, it was difficult to determine whether the content in the text editor was zoomed in or out. There was no visible indicator that explicitly showed the current zoom status.

In this release, we’ve introduced the Zoom widget, which appears at the bottom of the current text editor. It shows you the actual font size of the editor and helps you reset it to the default.

From this widget, you can navigate directly to Preferences/Settings, where you can adjust whether zooming should affect all editors or only the active one.

We’ve added a new Visual Studio 2022 keymap that resolves all shortcut differences between the current Visual Studio keymap and that of the Visual Studio IDE (e.g. Alt+Up/Down) in favor of the latter’s shortcuts. We recommend it for those who are accustomed to Visual Studio versions earlier than 2022 without ReSharper.

• We’ve split warnings for null checks on expressions that should never be null into two categories. The first warning is for expressions that are never null because an NRT annotation says so. The second warning is for expressions where there's an actual runtime check for null.
• We’ve added a new setting for switching to runtime enforced not null warnings only mode. It is accessible from the configuration item group in the Alt+Enter menu for annotation-based warnings.
• [MemberNotNull] and [MemberNotNullWhen] annotations are now supported in projects that don't use nullable reference types.

Here are some of the most notable features and fixes we’ve made for Razor and Blazor:

• We’ve added support for the new [EditorRequired] attribute from .NET 6. The corresponding inspection and quick-fix are also available if you try to use a Blazor component without specifying the required parameters.
• We’ve implemented long-awaited support for C# local functions inside Razor syntax.
• We’ve improved the Code Cleanup in .razor files with Blazor components. It no longer removes all @using declarations.
• We’ve also fixed the If To Switch and Invert If context actions in Razor code with references to Blazor components.
• Rider now uses the correct naming style for Blazor injected properties.
• The Comment with Line Comment action now comments only the part of the Razor code you’d expect it to.
• We’ve added navigation through inheritance hierarchy to Razor code. Now the corresponding gutter marks are shown for base and derived symbols. You can click them to navigate to the code.

• We’ve fixed various project model issues that could lead to freezes while projects were loading and updating, as well as issues that were causing analysis to ignore changes to projects or other files. We’ve also addressed the problems causing F# scripts to lead to non-working package references and other files’ include directives.
• C# projects now properly see InternalVisibleTo attributes defined in F# projects, so internal symbols can be accessed without resulting in errors in the IDE.
• We’ve fixed some issues with type providers, such as analysis errors that previously appeared in code with the same type provider instantiation.
• We’ve fixed the problem with the Rename refactoring as it didn’t work on some symbols.
• In addition to a variety of bug fixes across different parts of the F# plugin, F# support has received more analyzers and quick-fixes that suggest using recently added F# features. A number of existing features have been improved, as well. You can take a look at the full release notes for more information.

We’ve made a number of improvements for adding web references to .NET projects. Let’s have a look at the most notable ones:

• You can now add a web reference to .NET and .NET Core projects (previously, this was possible only for .NET Framework projects).
• You can add references from .wsdl files using the file path instead of the URL in the Add Web Reference dialog.
• If you add a WCF web service reference to a project, this reference appears in the Services node in the Solution View tool window.
• If the web service reference has basic authentication, Rider will display the dialog where you enter your credentials.
• net.tcp and net.pipe URI prefixes are now supported.

We continue to improve our Endpoints support and Endpoints Viewer. The viewer is now also aware of and collects endpoints for ASP.NET Core 6 minimal API routing and convention-based routing. This means that you can explore and navigate to these endpoints and use smart code completion, in addition to the features that were already available.

Rider 2022.1 comes with several improvements for Vue 3. If you define components as global, the IDE will now recognize them in your .vue files. Rider should also properly support the createApp syntax. It will correctly match applications created using createApp with their related elements. This version also includes support for Nuxt 3, a new version of a popular Vue framework.

If a Markdown file contains instructions with commands that you need to execute in your terminal, you can run those commands directly from the Markdown file using the run icons in the gutter.

We’ve added new options to the floating toolbar that will appear on text selection when you edit Markdown files. Using this toolbar, you can now quickly select header styles and create lists. You can customize this toolbar with the options you need. To do so, go to Preferences / Settings | Appearance & Behavior | Menus and Toolbars | Markdown Editor Floating Toolbar.

We’ve also added a new Copy code snippet action to Markdown blocks so you can easily copy contents to the clipboard.

We’ve implemented an option to mark code as “not coverable”. You can use it to exclude code that doesn’t need to be tested from the coverage process and get clearer snapshots. To use this feature, install the JetBrains.dotCover.MSBuild NuGet package and add the comments // dotcover disable/enable around the code. For more details, please check out this ticket.

We’ve moved the Preview Diff icon from the Commit toolbar to the menu, which is accessible by clicking on the Cog icon, and renamed it to Show Diff Preview on Single Click. Here you can specify the behavior you want to see when you click on a file in the Changes tree: the file can either be selected, or opened for diff preview.

We’ve improved the functionality of Annotate with Git Blame to make it easier to investigate introduced changes. Rider highlights the difference in lines right in the editor when you hover over an annotation, and when you click on it, the IDE opens the Git Log tool window.

Everyone knows that naming is hard. From time to time, you may even want to change the name of an entire solution. Rider can help you here. Call the context menu for the solution node in the Solution Explorer tool window, select Edit | Rename, and enter the new name for your solution.

We’ve added the SDK option as a dropdown list on the New Solution/Project dialog. It can help you create a project for older .NET SDK versions after installing the new one.

The Run Static Method action works for projects that target .NET and .NET Core. You can execute any static method right from the code editor by clicking the green “run” triangle on the gutter margin.

We’ve introduced several improvements for our support for Roslyn analyzers and source generators:

• Rider supports .globalconfig files for configuring code analysis rules from Roslyn analyzers.
• Rider now passes the correct language version to Roslyn analyzers.
• We have improved the loading and launching process of source generators and analyzers. There is no need to restart the IDE to resolve the generated code from source generators.

We’ve reorganized all the items in the Alt+Enter menu related to Code Cleanup and Formatting. The Format selection, Cleanup selection, and Apply syntax style were combined into one Reformat and Cleanup item to provide a single entry point.

In addition to these changes, the syntax style settings are now available in the Configure code style and Autodetect code style settings actions. The Preview code style panel shows changes in syntax style as well.