More Updates and Fixes for ReSharper and Rider 2025.2

Sasha Ivanova

A second set of updates and bug fixes for the 2025.2 release of ReSharper and Rider has just been made public. 

Let’s take a look at what’s been improved.

ReSharper 2025.2.2

To make your transition to Visual Studio 2026 seamless, ReSharper now installs a lightweight migration extension bundled with the product. This extension will be carried over automatically by Visual Studio when you upgrade to the 2026 release. You will then be able to launch the ReSharper installer for Visual Studio 2026 from the Extensions menu by selecting ReSharper Installer | Install ReSharper.

Notable fixes:

• We’ve introduced support for xUnit v3 3.x, so you can now run tests without compatibility issues when upgrading from earlier xUnit versions. [RSRP-501333] 
• The Search Everywhere dialog now auto-fills with the text selected in the editor in Out-of-Process mode. [RSRP-500894]
• There are no more false Cannot resolve symbol warnings for valid XML documentation references in C# code. [RSRP-501683]
• Licenses from the License Vault are once again applied automatically on Visual Studio startup. [RSRP-500218]
• Rider no longer incorrectly reports valid symbols as unresolved after updating to 2025.2.1, both in Visual Studio and when running InspectCode. [RSRP-501671]

For the full list of changes included in this build, please refer to our issue tracker.

Rider 2025.2.2

Junie is out of Beta

The AI coding agent by JetBrains now provides stable support across all languages and technologies supported in Rider.

.NET Aspire support

The bundled .NET Aspire plugin now comes with the Add .NET Aspire Orchestration action for creating, running, and managing Aspire projects directly from the IDE.

Major fixes included in this build:

• The working directory for .NET Run configurations now correctly points to the output directory (OutDir) instead of the project root when using launchSettings.json. [RIDER-128989]
• The Deployment mode dropdown in Run configurations no longer disappears when new configurations are added. [RIDER-128856]
• No more crashes when using autocomplete in C# code. [RIDER-129917]
• There are no more false Cannot resolve symbol warnings for valid XML documentation references in C# code. [RSRP-501683]
• The Flip context action now works correctly for method parameters in both declarations and invocations. [RIDER-126552]
• .uprojectdirs files now load correctly and no longer cause Rider to get stuck during the Loading projects step. [RIDER-129467]
• Running and debugging on Xbox once again works reliably. [RIDER-129942]
• Full line code completion (FLCC) no longer duplicates already typed symbols in the editor. [RIDER-122389]
• Scratches and Consoles files can now be added to Junie contexts without issues. [RIDER-128529] 

For the full list of changes included in this build, please refer to our issue tracker.

Subscribe to a monthly digest curated from the .NET Tools blog:

Subscribe form

By submitting this form, I agree to the JetBrains Privacy Policy Notification icon

By submitting this form, I agree that JetBrains s.r.o. ("JetBrains") may use my name, email address, and location data to send me newsletters, including commercial communications, and to process my personal data for this purpose. I agree that JetBrains may process said data using third-party services for this purpose in accordance with the JetBrains Privacy Policy. I understand that I can revoke this consent at any time in my profile. In addition, an unsubscribe link is included in each email.

Submit

Thanks, we've got you!