Hi, thanks for sharing this issue.

Yes, v3.10 did fix the issue. Unfortunately the fix is a moving target, and MS do release new versions of .NET Core all the time. I'm not going to rule out the possibility that it has been rebroken due to platform level changes, or that there is an edge case that hasn't been considered.

I just wanted to check that you have the 'Copy referenced assemblies to workspace' setting turned on for all the projects in your solution?

Thanks for confirming this.

Where we've experienced it before, this problem has been tied to the structure of the relevant .deps file inside your project's build output directory. Normally, this .deps file should specify the dependencies that sit under the DependencyContext. We do quite a bit of processing on the file to allow us to compartmentalise the build system but still have the runtime environment behave more or less the same as it would normally.

The unfortunate problem with the dependency structure detailed in this file is that it's extremely complex, to the point where without a scenario demonstrating the problem, we really have no hope of being able to track it down or resolve it.

If you're able to build a sample solution to reproduce the issue you're seeing here, I should be able to pull things apart and figure it out. You're welcome to submit small test solutions through the NCrunch contact form.

Thanks! I'll take a look at get back to you as soon as I have more info (or a fix).