What's New in Rider 2025.1

Navigate your entire codebase with Rider's new Files view. This redesigned view lives alongside your Solution view. The Files view shows your complete repository structure from the root, making it easier to work with full-stack projects, configuration files, and everything else that makes up your modern development environment. To enable repository-wide visibility, select New Files View in the Solution Explorer tool window settings.

You can now view and explore C# syntax trees directly inside the IDE with Rider's new Roslyn syntax tree visualizer. The visualizer provides real-time tree visualization that stays synchronized with your editor.

You can interactively explore nodes and inspect their properties, quickly navigate between code and corresponding tree nodes, and use comprehensive search and filtering capabilities. Learn more.

Starting with Rider 2025.1, remote development on Windows hosts is now supported via the JetBrains Toolbox App. While Gateway remains available for Linux connections, the full transition to the Toolbox App as the primary hub for remote development is underway. Learn more about how you can use the JetBrains Toolbox App to connect to Windows, macOS, and Linux host machines from this blog post.

Rider now integrates with the Unity Profiler, bringing CPU performance insights directly into your editor. The IDE fetches CPU usage snapshots and displays them inline with your code, making it easy to spot performance hotspots as you write and debug your Unity scripts. You can navigate seamlessly from calls in the Unity Profiler hierarchy view to their corresponding methods in Rider.

More updates for game development

• Support for project templates from the new SDK.
• The ability to create, run, and debug projects targeting the new SDK.
• Initial support for the latest preview features of both C# 14 and VB 17.13.

Rider 2025.1 brings initial support for .NET 10 and C# 14 preview features, helping you stay ahead of the curve with the latest language enhancements.

Previously, using nameof required specifying all type arguments, causing unnecessary verbosity. C# 14 allows nameof(List<>) without explicitly listing type arguments. Rider now detects redundant generic type arguments in nameof expressions and provides a quick- fix to simplify them.

C# 14 introduces new implicit conversions between ReadOnlySpan<T>, Span<T>, and T[], making span-based code more intuitive. Rider now fully supports these conversion rules, helping you write efficient, modern C# code.

Learn all about the improvements to C# language support in Rider and ReSharper on our blog.

We've rewritten various parts of F# code completion, so it now works faster, uses less memory, and provides more accurate suggestions.

We've optimized building metadata, fixed issues leading to inconsistent analysis and freezes, and improved cancellation for better code editing performance.

More information about other bug fixes and improvements for F# support can be found here.

For Windows and Linux users, the IDE now offers a new option to merge the main menu with the main toolbar, creating a more streamlined interface.

You can set Rider to automatically update plugins in the background. It will download all available and compatible updates and apply them the next time the IDE is restarted without additional notifications.

For this release, we've completely overhauled our string interning system. IDEs process an enormous number of strings, including source code, syntax elements, symbol names, and file paths, so efficient string handling is critical. Our new string interning system stores, on average, four times as many unique strings as its previous iteration and consumes about half as much memory to do so, freeing up resources in large-scale .NET projects.

Razor tag helpers and Blazor component support have been completely rebuilt for 2025.1. This long-needed overhaul brings a 5%–10% reduction in analysis time for large ASP.NET solutions with heavy component usage. You'll also experience fewer reanalysis events when editing .cshtml/.razor files, as well as significantly reduced false error reporting.

For the 2025.1 release we have focused on improving AI-based completion in the context of web framework components. These changes affect local full line code completion as well as cloud-based completion suggestions.

Rider now ensures that AI-generated unit tests follow existing naming conventions in your project. This improvement helps maintain consistency across your test suite, reducing the need for manual renaming and making test integration smoother and more intuitive.

Learn more about the AI Assistant features from this page.

Rider now offers automatic attachment to child and grandchild processes during .NET application debugging. When enabled in the run/debug configurations, the IDE tracks and attaches to all .NET processes spawned within the application's process tree.

Enable this feature using the new Attach to child .NET processes checkbox.

Rider 2025.1 comes with improved data visualization for LINQ expressions, making it easier for you to understand and debug complex LINQ queries directly in the debugger. You'll now be able to inspect query execution, see intermediate results, and better understand how your LINQ operations transform the data. For more information, please see documentation for this feature.

Rider 2025.1 introduces a dedicated run and debug configuration for dotnet watch, streamlining the development workflow for projects that need automatic rebuilding and restarting as code changes.

This enhancement particularly benefits ASP.NET Core and .NET developers, as it continuously builds your application when you modify .cs, .html, or .css files. The feature also extends to test files, enabling automatic test execution whenever your code changes.

Input and output redirection for run configurations is available in Rider 2025.1. You can now easily specify a file to be used as standard input (stdin) and direct program output to a file, streamlining debugging and testing workflows.

Additionally, you can now attach log files to a run configuration. These files will then be shown in separate tabs in the Run or Debug tool windows during program execution.

Rider 2025.1 simplifies the management of environment variables. Instead of manually entering variables, you can now use .env files directly in your run/debug configurations. Look for the folder icon (Browse) next to the Environment Variables field to attach your .env files. Rider will load them on the next launch. You can even use multiple files across different projects to maintain consistent configurations.

You can now see commit details directly in the diff view. The diff dialog now displays the commit message, author, date and time, and full commit hash, giving you a clearer view of a file's history and helping you understand modifications faster.

You can now launch any tool to perform a pre-commit check alongside inspections and formatting. Custom checks can be configured as run configurations in the Run Configuration dialog. This helps you catch potential issues early and ensures your code meets project standards before it's committed.

For more information on VCS updates, please see this page.

We've added support for the NoesisGUI framework for both Unreal Engine and Unity projects.

Rider's remote development support now works better with Unity projects. Specifically, the shader variants selector is now available, and the Unity Explorer view will now correctly select the open file.

We've made some fixes to the Rider package bundled with Unity. For example, root namespaces are no longer occasionally missing, the Unity editor log file can be opened directly from the Unity settings page, and Rider entries are no longer duplicated on Linux.

Rider 2025.1 now supports running and debugging Azure Function projects via the .NET Aspire and the Azure Toolkit for Rider plugins. Please share any feedback you might have on the functionality in the comments on this ticket.

The .NET Aspire plugin now also supports running and debugging AWS Lambda Function projects in Rider. For more information, please see this GitHub issue.

Rider 2025.1 now supports remote debugging of Azure App Services projects via the Azure Toolkit for Rider plugin (Azure Functions and Azure Web Apps are supported).

Rider 2025.1 introduces proper support for Blazor WebAssembly (WASM) publishing. You can now use the .NET Publish | Publish to Folder configuration, which will use browser-wasm target runtime without encountering missing files in the output.

Rider now prioritizes service-powered quick fixes, especially for imports, when internal suggestions are unavailable. This ensures that relevant fixes appear first, reducing friction in resolving issues and improving the overall coding experience.

For more detailed information, visit the What's New in WebStorm page.

Previously, to start a Code With Me session in Rider, you had to manually enable it using the Enable Code With Me action and performing a restart. In Rider 2025.1, this step is no longer necessary — you can start a collaborative session right away without restarting the IDE.

JetBrains terminal: New architecture Beta

The 2025.1 release introduces the reworked terminal architecture, which is available in Beta. The terminal now runs on a stable, standards-compliant core and uses the IDE's editor to render the UI. This change lets us introduce new features while preserving compatibility and performance across various platforms, whether local or remote. Get more details about our plans and progress in this blog post.

Rider 2025.1 brings several improvements to the decompiler, enhancing support for the latest C# features and improving code readability. Here's what's new:

• Support for required members.
• Added support for the new System.Threading.Lock type introduced in C# 13.
• Support for ref fields and scoped parameter modifiers.
• Support for allows ref struct generic anti-constraint.
• Pattern-based using for ref struct types.
• Support for string interpolation.
• Certain integer constants in decompiled code now include commented hexadecimal representations for better readability.
• Support for file-scoped namespaces.