Release notes for 5.0.0.2
-----------------------------------------------------------------
*****
This version of NCrunch introduces changes to the grid protocol. This means that grid
node servers must be updated before they can be used with the new version.
*****
This is a major feature release containing two new feature areas: Runtime Data Inspection, and support for JetBrains Rider.
Please see https://blog.ncrunch.net/post/NCrunch-V5-Now-Available.aspx for more information about these two new features.
When Runtime Data Inspection is disabled and the product is running under Visual Studio, the behaviour of this build will be almost identical to v4.19.
Other fixes and improvements included in this release are below:
-----------------------------------------------------------------
Fixed an issue where specifying a 'TargetFrameworks' with a leading or trailing semicolon inside project XML would cause load errors.
Adjusted the error handling around CPU core allocation settings to give a better experience if these settings go wrong.
Fixed a potential crash issue that could occur when using the AdditionalFilesToIncludeForGridProcessing with files that are being locked and changed while the engine is active.
Implemented a speculative fix to try and resolve data inconsistencies between the NCrunch client and grid nodes caused by differences in environment, i.e. net6 engine vs net4 grid node
Adjusted the corner spinner so this will now show multiple spinners during engine startup, one for every background task.
Fixed an issue where projects making use of the Implicit Project Dependencies and Copied Project Dependencies settings could encounter settings reload loops that could cause engine instability.
Fixed an issue that was preventing Azure function projects from building correctly under net8.0.
Fixed an issue that would cause NCrunch to fail to correctly load .cache files in excess of 2.1GB.
Fixed an issue where referencing a C++ project from a project being used by NCrunch could result in PDB reader exceptions.
Fixed a performance bottleneck that could cause engine efficiency to degrade while under extremely heavy load
Renamed the 'CPU Cores Assigned to Visual Studio' setting to 'CPU Cores Assigned to IDE'. Setting values under the previous name will be automatically ported to the new one.