- Added a new adapter to integrate NCrunch with Xunit v3
- Removed forwards compatibility with JetBrains Rider 2024.3 EAP, there are currently integration problems prevent us from integrating with this version properly.
- Improved the rendering of the coverage markers under Rider. RDI Scope end markers were rendered a bit smaller then the other markers. Also the markers were lightly scaled when rendered.
- Fixed a race condition that could cause NCrunch to become desynchronised with the contents of editor windows under Rider when source files were renamed.
- Adjusted the automatic selection of .NET SDK version for VS2019 so that this will revert to the 'default' chosen by the platform, rather than trying to override it to prevent disfunctional behaviour when tools are in a preview state. This should give more stable out of the box support when using NCrunch with VS2019 when VS2022 previews are installed.
- Adjusted coverage mapping to make it more resilient when faced with map sequence discrepancies between clients and grid nodes for multi-targeted projects being double-referenced implicitly.
- Fixed the Tests Window under Rider from flickering when the window was split horizontally.
- Under Rider context menus now stay open when the mouse is over sub menus. When a context menu is opened there is no longer a task bar icon appearing.
- Fixed an issue where the removal of an RDI filter target from the source code could result in RDI frames failing to open until the engine was reset.
- Fixed the RDI error message not showing when opening an RDI frame under Rider.
- Fixed high DPI issues on the About, License, Add Gridnode, Submit Bugreport and License Entry Windows.
- Fixed the Additional Files to Include configuration editor when showing it with different UI scaling configurations under both Rider and Visual Studio.
- Fixed an issue where reference trees from implicitly referenced projects were being passed into the runtime assembly loader. Under certain circumstances (such as the loading of NUnit), this could cause the runtime to attempt to load these assemblies erroneously into the application domain, causing stability issues in the test environment.
- Improved the error handling for internal NUnit issues kicked up through skipreasons. These will now be reported as analysis errors by NCrunch.
- Fixed NCrunch unable to build Azure Functions projects using v1.17.0 of the SDK.
- Fixed an issue that was causing Azure Function projects to fail to build on v1.17.2 or above of the SDK.