More Updates and Fixes for ReSharper and Rider 2025.3

Sasha Ivanova

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

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

ReSharper 2025.3.0.2 

• Visual Studio 2026 no longer displays the warning that ReSharper uses the deprecated IQuickInfoBroker API. [RSRP-502236]
• Fixed an issue where MSTest v4 tests were duplicated in the Unit Test Explorer. [RSRP-502145]
• Automatic import of missing namespaces now works correctly again. [RSRP-502252] 
• We’ve fixed false positive analysis warnings for get-only setters in .NET projects. [RSRP-502278]
• External services for grammar, spelling, and SQL analysis now start correctly when multiple Visual Studio instances are open simultaneously. [RSRP-502249]
• Icons for context actions and inspection configuration are now visually distinct again in the Alt + Enter menu. [RSRP-502012]
• The license agreement dialog for language dictionaries now displays correctly when the Windows dark theme is used. [RSRP-502248] 
• Fixed a crash caused by a stack overflow in C# code analysis when resolving overloaded operators. [RSRP-502244]

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

Rider 2025.3.0.2

• Authentication for private Azure DevOps NuGet feeds now works correctly again. [RIDER-132336]
• Rider now correctly uses the user’s installed .NET SDK instead of its own bundled one when compiling projects. [RIDER-131155]
• Automatic import of missing namespaces now works correctly again. [RSRP-502252] 
• We’ve fixed false positive analysis warnings for get-only setters in .NET projects. [RSRP-502278]
• Fixed a crash caused by a stack overflow in C# code analysis when resolving overloaded operators. [RSRP-502244]
• Errors caused by missing or incomplete results from source generators have been resolved. Projects using .NET source generators or libraries like Vogen now load and analyze correctly without showing false red code. [RIDER-132269]
• Quick-fixes that rely on Roslyn analyzers now work correctly with the Microsoft.CodeAnalysis.CodeStyle package. [RIDER-132263]
• We’ve also resolved a couple of issues that used to cause long freezes. [RIDER-132136, RIDER-130284]

For the full list of issues we’ve resolved 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!