Hi,

NCrunch doesn't function well with Nuget package restore (command-line, MSBuild or otherwise), as it needs to build new workspaces regularly to be able to build and run tests in parallel. Since these workspaces are effectively clones of your source project, newly creating them simply means that Nuget needs to restore the packages again and again, greatly slowing down the build and increasing the amount of disk space unnecessarily allocated to the workspaces.

When working with NCrunch, you should always restore your packages inside the foreground solution instead. NCrunch will detect the changes made by packages being restored and should resynchronise accordingly. In any even that Nuget operations cause a desync, simply resetting the engine will bring it back into line.

There are sometimes situations where NCrunch can't correctly detect all the Nuget dependencies of a project. This can sometimes result in build errors. If you get hit by this, just include the relevant Nuget paths using the Additional files to include project-level configuration setting.

NCrunch has two kinds of 'solutions' it works with (when you're not using distributed processing):

1. The 'foreground' solution - this is the solution that you open up in Visual Studio and make changes to. It's effectively your codebase. NCrunch will never make modifications to it but it will read any changes that are made and synchronise them into ...

2. The 'background' solutions / workspaces. These are virtual projects/solutions that are constructed inside a separate working area of your hard disk. NCrunch modifies these routinely to create transient copies of your source code. When NCrunch builds your projects and runs tests, it will do so here.

Because the 'foreground' solution is the source of all data for NCrunch, it's reliant on this solution to contain everything it needs to build your projects. In earlier versions of the product, NCrunch had no knowledge of Nuget and did not attempt to override any build steps. This meant that when NCrunch loaded up a foreground solution without the Nuget dependencies restored, Nuget would then attempt to restore its packages inside the background workspaces, which was very slow and inefficient. To prevent this from happening, NCrunch will now suppress the automatic package restore of Nuget inside background workspaces.

This means that for NCrunch to work, it needs to have all the Nuget dependencies restored inside your foreground solution. Otherwise, it will complain about missing dependencies and it won't be able to build your projects. The rule of thumb here is that if your foreground solution can build inside Visual Studio (without NCrunch involved), then you're OK here, as all the dependencies will have already been restored. If your foreground solution won't build in Visual Studio and Nuget is giving you errors, then NCrunch won't have any way to solve this for you with its own background processing.

It's likely that your problem isn't related to the restoration of Nuget packages, and is probably just an implicit build reference into other areas of the package. Try including your Nuget 'packages' directory using the NCrunch solution-level 'Additional files to include' setting. This will instruct NCrunch to copy ALL the Nuget package resources into each workspace.

If this solves the problem, you can then narrow down the dependency to specific files to include instead, as copying all Nuget packages into each workspace can slow the engine down a bit.