ReSharper C++ 2025.3.2

2025.3.2
Fixed 6
  • InitializeComponent calls in .NET MAUI projects are no longer incorrectly flagged as errors by code analysis
  • The ConstantExpected inspection now respects the [ConstantExpected] attribute transitively and no longer raises warnings when values are passed through annotated parameters
  • The OutParameterValuesAlwaysDiscarded inspection no longer reports false positives for out parameters used in C# 14 extension member syntax
  • Recursive calls are now correctly indicated in the gutter for C# extension members
  • The bundled Unity plugin now works correctly in ReSharper Command Line Tools
  • Fixed an issue that could prevent memory profiling from starting on systems where the Microsoft-Windows-RPC ETW provider is already in use

From ReSharper C++

ReSharper 2025.3.2 These are the most notable bug-fixes included in this build:

  • InitializeComponent calls in .NET MAUI projects are no longer incorrectly flagged as errors by code analysis. [RSRP-502255]
  • The ConstantExpected inspection now respects the [ConstantExpected] attribute transitively and no longer raises warnings when values are passed through annotated parameters. [RSRP-502500]
  • The OutParameterValuesAlwaysDiscarded inspection no longer reports false positives for out parameters used in C# 14 extension member syntax. [RSRP-502536]
  • Recursive calls are now correctly indicated in the gutter for C# extension members. [RSRP-502225]
  • The bundled Unity plugin now works correctly in ReSharper Command Line Tools. [RIDER-134769]
  • Fixed an issue that could prevent memory profiling from starting on systems where the Microsoft-Windows-RPC ETW provider is already in use (for example, by security software). [DMRY-13484] For the full list of resolved issues included in this build, please refer to our issue tracker.
View original

Upgraded? How did it go?

Discussion