Hi, thanks for posting.

When you switch between build configurations, how are you handling this in NCrunch? Do you use the 'Use Build Configuration' setting? Note that NCrunch doesn't track the selected build configuration in the IDE - it will always use the project's default configuration.

The actual default depends on how the project is designed. I suspect you're encountering a variation of this problem, though I find the symptoms a bit strange and it makes me wonder if perhaps you have other build logic or package references dependent on the configuration.

Try setting NCrunch's 'Use Build Configuration' to 'NoLicense' to see if this makes any difference for you.

Sort of. In this case it's most probably an inconsistency between the dependency data from Visual Studio (project.assets.json) and the build configuration.

I expect VS would likely set up its dependency data according to the selected build configuration in the IDE. NCrunch relies on this data to be fed downstream because it can't safely generate it itself. When you have dependencies from one build configuration being fed into a build system running on a different build configuration, weird stuff can happen.

Try to keep your NCrunch build configuration identical to the one selected in VS. If you continue to have problems, I recommend adjusting your logic so that your dependencies are the same between configurations but your code is different (i.e. use compiler conditionals instead of build conditions).