Hi Mark,

Unfortunately I can't seem to find this package in the nuget directory as expected, so I haven't been able to reproduce the issue myself ... however, my first guess would be that this package is making assumptions about output assemblies being co-located: http://www.ncrunch.net/documentation/considerations-and-constraints_assembly-colocation-assumptions.

I recommend to try turning on the 'Copy referenced assemblies to workspace' for all the projects in your solution - http://www.ncrunch.net/documentation/reference_project-configuration_copy-referenced-assemblies-to-workspace.

Failing this, compatibility mode may help to narrow down the problem - http://www.ncrunch.net/documentation/troubleshooting_compatibility-mode.

Hi Mark,

Thanks for the Nuget link. I'm not sure why this wasn't showing up via a Nuget search, but I've managed to install the package and can confirm that this is a dependency resolution issue that can be solved by including the necessary dependencies using the 'Additional files to include' setting.

Although such an issue is no doubt a cause of frustration when trying to use these sorts of packages with NCrunch, unfortunately it is not possible for NCrunch to resolve these dependencies on its own. NCrunch relies on the build process to identify the dependencies of projects. Where dependencies are not consistently declared inside the build process (as can be the case with certain files accessed via custom-made build tasks), NCrunch has no way to generically identify them.

The only solution would be to deliberately hard-code identification routines into NCrunch that are suited to each package, detailing which files should be included per package. This would be akin to trying programming a VCS with enough intelligence to identify which files were source code and which weren't, by trying to code use-case scenarios for every possible programming language used by the VCS.

Thus the 'workaround' described is in fact the correct solution. By using the 'Additional files to include' setting, you are effectively telling NCrunch which files need to be included in its workspaces. It's perfectly OK to do this. Very often there is no other way for the tool to be informed of which files are needed in a complex build such as this.

I've added a feature request https://ncrunch.uservoic...ers-during-ncrunch-build

Thanks, that seems to work for me.
Would it be possible to make this built into NCrunch? I'm probably being very lazy, but I'd prefer not to have to go through cs-projs for a VS extension (even when it's as awesome as NCrunch)

Hi there

the fix worked well for me for StyleCop.Analyzers Beta 15, but with the version Beta 16+ they have changed how the settings file has to be included:
https://github.com/DotNe.../EnableConfiguration.md

Since this change ncrunch is not able to build anymore. This is what I get in the output:
CSC (0, 0): Source file 'C:\Users\chbehus\AppData\Local\NCrunch\22312\24\project\..\stylecop.json' could not be found.
WARNING - CSC (0, 0): Analyzer 'StyleCop.Analyzers.MaintainabilityRules.SA1402FileMayOnlyContainASingleClass' threw an exception of type 'System.NullReferenceException' with message 'Object reference not set to an instance of an object.'.
...

I tried with the newest version of ncrunch and it still happens.

Do you have any idea what causes this and how to fix it?
I really would like to be able to to use ncrunch again ;-)

Regards

Hi

indeed this seemed to have fixed the problem.
I wasn't aware of the existence of this setting, otherwise I probably would have tried before posting here

Anyway thank you very much for the quick reply and keep up the good work :-)