I installed the new release of NCrunch. Unfortunately, it doesn't work on my computer. I have Visual Studio 2013 installed, with .NET 4.5.2:
An error occurred while analysing this project after it was built: NCrunch encountered an unexpected error occurred while building an environment to analyse an assembly: System.Exception: The requested version of the .NET framework, 'Framework453' is not installed on this system
at nCrunch.Core.ProcessManagement.ExternalProcessManager.(ProcessorArchitecture , ProcessLoadParameters )
at nCrunch.Core.ProcessManagement.ExternalProcessManager.LoadExternalProcess(ProcessLoadParameters parameters, GridClientId client)
at nCrunch.Core.TestManagement.TestRunnerProcess.(Boolean , FilePath , GridClientId , CustomEnvironmentVariable[] )
at nCrunch.Core.Processing.AnalysisTaskLogic.DoProcessTaskAndReturnSuccessFlag()
Additionally, this error text is shown in the NCrunch Tests window, but in the NCrunch Processing Queue window, it only shows the tasks as failed, without any output text.
NCrunch doesn't have a task runner that caters specifically to .NET 4.5.2, so it instead relies on 4.5.3 as a fallback.
Installing the .NET 4.5.3 SDK should resolve this problem. Otherwise, if the .NET 4.5.2 features are not important in your test project, targeting the test project to .NET 4.5.1 will also work.
Daniel Rose wrote:Retargeting everything just to solve this problem seems overkill to me. Why is it falling back on 4.5.3, which is in preview state?
4.5.3 is the highest available framework supported by NCrunch, and it supports 4.5.2 features ... so it isn't the ideal solution, but it should technically work. The fact that 4.5.3 isn't installed on many systems is an oversight. I think a set of 4.5.2 task runner will need to be added. It looks like we're going to need a whole library of task runners at the rate that MS is releasing new .NET versions right now.
would be really good to have a set of 4.5.2 task runners. I cannot upgrade to 4.5.3 because some 3rd party assemblies/tools have (build) issues with that. So I need to stick to .NET v4.5.2. But that means that I cannot use the NCrunch grid testing functionality anymore (without downgrading to previous "RC" NCrunch version which I have to do by now).
It looks as though 4.5.2 is an in-place update over 4.5.1... At least, when constructing a 4.5.1 test environment on any machine with 4.5.2 installed, it seems to contain the same features and reference the same .NET assembly versions.
So I guess for effective purposes, 4.5.2 is the same as 4.5.1.
I've introduced a fix that retargets the TaskHost to 4.5.1 instead of 4.5.3. You're welcome to give the build below a try to see if this works for you: