Hi, thanks for sharing this issue.

Does adding your entire packages directory to your 'Additional files to include' setting make any difference here? From what I can establish by googling around, it seems that this build target is trying to find the DLL using a relative file path, which suggests that making sure the file is copied to the NCrunch workspace should resolve the issue.

I recommend having a read up on how NCrunch uses its workspaces and how to best control them:

Workspaces
Implicit file dependencies
Additional files to include

You should avoid making any changes to workspaces created by NCrunch. The files in workspaces should never be manipulated directly and should only be touched by the NCrunch engine itself. In the case of the issue you're solving, the most important thing is that NCrunch is aware of ALL the files that need to exist in each project's workspace in order for the project to be successfully built by MSBuild. Somehow, there's a reference here that's being missed. If you can ensure NCrunch is made aware of this file using configuration, it can be copied into the workspace where it will be found at build time. Adding your entire packages directory to the 'additional files to include' setting is usually a blunt way to ensure nothing is being missed, as the dependency structures in the build system can sometimes be quite complex and simply including the missing file on its own may not always be enough.