Hi, thanks for posting.

I am unfamiliar with this particular framework, which makes it hard for me to give specific advice on its limitations in regards to NCrunch. However, it looks to me like the framework is designed to treat the solution as a single cohesive unit (based on the need to inject the solution directory). This sort of structure isn't something that is supported under NCrunch, because we separate projects from the solution and into background workspaces where they can be crunched in isolation.

I recommend having a look at NCrunch's project atomicity constraints, and make sure you are aware of how absolute file references work in NCrunch. It may be that you can rig something up with copied files or references to the foreground solution that might give some degree of a workaround.