Would you be able to submit a bug report after you've had this blow up? The log may yield information on which dependency is missing.

Thanks. Something seems different about your setup. I can see files resolving to [user]\.dotnet\NuGetFallbackFolder. Have you redirected your nuget packages directory somewhere else? If so, how has this been done?

NCrunch always considers the root of Nuget packages to be at [User]\.nuget\packages. In truth, I did not know it was possible to redirect this elsewhere. The log attached to the report you submitted indicates that MSBuild is resolving references to the [user]\.dotnet\NuGetFallbackFolder instead of [User]\.nuget\packages, so I presume there must be some additional package search logic on your machine allowing the MSBuild steps to find packages from outside their usual location.

Because NCrunch assumes that the Nuget packages will only be under the default location, some of the logic used to set up a runtime environment for you is malfunctioning. I'm not sure yet if this is the reason for the runtime environment exploding immediately on initialisation, but I'd say it's a strong candidate.

Is moving all packages to [User]\.nuget\packages and removing your fallback directory an option? I'd really like to see if this solves the problem.

Can you try also removing the NuGetFallbackFolder, or placing it somewhere else on disk where you can be sure it won't be picked up by any implicit search logic?

It's important that NCrunch is able to recognise the dependencies as being Nuget packages, which can only happen if they are loaded from .nuget.



Edit: Something else worth doing is to make sure you clear out your project lock files (project.assets.json) and any of their associated generated files then get VS to rebuild them. There might still be bindings reaching from there to the fallback directory.