Hi, thanks for sharing this issue.

Looking at the paths here, I think this is failing due to NCrunch's project atomicity constraints. You have a relative path that points to the output of another project in your solution, which under NCrunch is going to land at an undetermined location.

In most situations the 'Copy referenced assemblies to workspace' setting would solve this problem, but because weavers tend to happen at build time rather than run time, any build steps that copy the dependency into the project's output directory won't have run yet.

It's possible to add the weaver assembly to the 'Additional files to include' setting for the project, and in theory this will work around the problem, but it will require you to rebuild the weaver in your IDE every time you make changes to it (not ideal).

The ideal solution to this will come down to Fody's search logic at build time. Does introducing a project reference to the weaver resolve the issue?