Hi,

This is a simple file resolution issue, as these analyzers are access indirectly and NCrunch cannot automatically resolve them. The solution is simply to include the analyzers using NCrunch's 'Additional files to include' setting. See http://www.ncrunch.net/documentation/considerations-and-constraints_implicit-file-dependencies for more information.

Not exactly. The projects and assemblies referenced by your solution are fine, and NCrunch has detected them. The analyzer assemblies are different as they are referenced by code included inside the build process - they aren't actually 'declared' dependencies.



A few people have been hit with this, so it does seem to be a common problem with the newly introduced analyzers. The NCrunch approach with undeclared dependencies (such as those deep within build steps) has been to simply try and educate people about implicit dependencies so that they understand how to correct the problem manually.

I guess a good comparison could be something like a VCS. Most VCS software is reliant on the developer to declare which files are actually source code and therefore should be introduced to the VCS. It could be considered possible for VCS software to try and determine this programmatically (for example, by parsing solution and project files or by using wildcards), but this would never be 100%. NCrunch follows the same logic - for the sake of convenience, it does its best to try and determine which files should be in the workspace and which shouldn't. In some ways it's a testament to how well it does this that people hit situations where files haven't been automatically resolved and feel it to be a defect in the product.

I'm looking at ways in which this can be improved for certain Nuget packages, but it's hard to do this reliably without unnecessarily bloating the workspace with unneeded files.