Directory.Build.props and ReferenceProject entries

Hi,

It seems as though NCrunch is losing referenced project references when they come from a Directory.Build.props file, rather than a .csproj file directly.

I've stripped a sample project back to about as bare-bones as possible to show what I'm trying to do... source is here:

https://github.com/kieronlanning/ncrunch-directory-build-props

The long and the short of it is that NCrunch seems to lose location information about csproj, but VS, MSBuild, dotnet and ADO all seem to work (that's just an FYI to show I've tried other tools).

Hi, thanks for sharing this.

Unfortunately, we cannot support a use case where project references are defined in included imports (such as directory.build.props). This is because NCrunch's manipulation and workspacing only targets project files, and it's assumed that any project references will be defined in these project files. Sorry we cannot support this.

Ahh, well. Thanks for checking!

It's a shame, because it's a pattern that works really well on large projects (made up of many solutions, using the Directory.Build.props via a git submodule).

b33rdy wrote:Ahh, well. Thanks for checking!

It's a shame, because it's a pattern that works really well on large projects (made up of many solutions, using the Directory.Build.props via a git submodule).

Sorry :( I understand the appeal. We've been wanting to do something similar for our project(s) too, but handling this involves busting through some very big abstractions .. and potentially causing some very big problems.