Hi,

I'm working with a large solution that contains an intentionally setup project that serves as the "master" project for all NuGet dependencies. It contains no code, and is the first project in the solution's build order. As an artifact of its build, copies of its referenced assemblies are copied into a unique output folder (which is not shared as the output folder by any other project in the solution). All other projects in the solution then reference their dependencies in this special output folder (rather than individually using NuGet). The intent, as I understand it, is to have a single point of control for versioning NuGet dependencies.

I've recently started using NCrunch on this solution, and am receiving a large number of warnings:

It has been detected that this component is referencing assemblies within the build output directories of projects within this solution. It is strongly recommended that assemblies are referenced from a directory location that is not subject to disruption from the build process.

Directly referencing assemblies that are updated, copied or manipulated by the build of projects in this solution will create implicit build dependencies that cannot be tracked by NCrunch or MSBuild. This can result in inconsistent build behaviour patterns and code versioning issues. It can also cause problems when trying to execute a clean build of the solution after it is checked out of a source control system.

I noticed that I can rt-click each warning, and select "Hide selected warning". I'd prefer to not hide that warning for all projects, because upon inspection, it did actually highlight a couple of legitimate problems where assemblies were being referenced in the common build output folder.

Is there any way to preserve this warning check, but whitelist a specific folder so that it does not trigger the warning?

Thanks!