I can't seem to make NCrunch (2.26) use the 4.6.2 version of its engine, even though the framework is properly installed, as well as its dev (and targeting) pack. It keeps using the 4.6.1 version.

However using a grid node on a 2008 r2 server with the 4.6.2 framework installed does use the 4.6.2 version properly. But locally, it always ends up in an analysis failure "The requested version of the .NET framework, 'Framework462' is not installed on this system"

This is on a Win10 x64 Enterprise (with all updates) with VS2015 Enterprise. I've just reinstalled the entire system (clean install, up to and including recreating the partition, can't do much cleaner than that :) from the Win10 anniversary update ISO. Even with only that, VS2015, ReSharper and NCrunch, the 4.6.2 engine is still not being used.

This happens on any project, even just creating a new class library and adding the NUnit package (or xUnit, doesn't matter). The project is created targeting the 4.5.2 framework by default, NCrunch when enabled starts up the 4.6.1 host and a 4.5.2 runner, and when switching the project to 4.6.2... no more NCrunch.

The 4.6.2 framework does work properly, can be use to compile and run the projects without any issues, the ReSharper test runner works fine with it, it's just NCrunch that doesn't seem to like it.

I may be missing something obvious but I'm currently out of ideas.

2.27 uses the 4.6.2 engine without problem, thanks :)

v2.27 has now been fully released - https://www.ncrunch.net/download.

Excellent! :)



Yes, this is by intention. See here for more details.

Hi Rupert,

When creating a test environment, NCrunch will always use the version of .NET targeted by the test project.

This means that if you have a test project targeting .NET v4.6.2, you will need to have .NET v4.6.2 installed. NCrunch detects v4.6.2 by inspecting the "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Release" registry value. For v4.6.2 to be installed correctly, this registry value must be 394802 or above (according to MS specs). If you have v4.6.2 installed but the registry key is lower than this value, you probably have a broken installation of .NET v4.6.2 and may need to reinstall it.