Hi, thanks for posting!

The correct behaviour is for NCrunch to look up a copy of the file inside its workspace. In this way, it works completely in isolation from your code.

With this in mind, NCrunch is already looking in the right place. The problem is that the file hasn't been copied there.

There are a few ways you can handle this. If your code relies on a file that isn't included in any project file, NCrunch considers this to be an 'Implicit dependency'. You can read more about implicit dependencies and how to resolve them here - http://www.ncrunch.net/documentation/considerations-and-constraints_implicit-file-dependencies.

If for some reason you don't want NCrunch to copy the file to the workspace (for example, if it's really big and copying it just isn't resource efficient), the NCrunch.Framework.Environment.GetOriginalSolutionPath() can be used to find your original solution when running inside NCrunch's test environment.