Hi, thanks for posting!
This particular build targets takes a range of properties as input, including what appears to be lists of assembly references. I don't think it was designed with NCrunch's workspacing in mind; possibly it assumes that referenced assemblies are co-located with the project being built.
I'd recommend trying NCrunch in
compatibility mode to see if there is a setting that works around the problem.
It may be necessary to disable this build target to allow NCrunch to work for your projects. You can do this by adding
conditional logic to your build to prevent certain parts of it from being executed by NCrunch. This could be done with a condition on the target itself, or alternatively on the <Import> statement used to include the .targets file inside the build.