Good morning,

We have a fairly large solution in which we typically develop (around 200 projects). Most of those are demo/example applications, a few are the library we're actually developing, and a few are test projects. So far I've manually excluded each and every demo application from NCrunch (because they contain no tests and are basically irrelevant here). However, that's about 130 individual `.v3.ncrunchproject` files and every time a new project is added, we have to exclude it as well.

So is there a more elegant way here? Can I apply NCrunch project-level configuration based on file system location, e.g. by adding a configuration file in the directory where all the to-be-ignored projects reside? Or is there a way of having a list of projects to ignore in a central location that supports wildcards? I could also do this with MSBuild properties if that is an option.

Since we're just two team members using NCrunch (the others seem to be fine not running tests or having to wait each time), I'd like to spare them from regularly having commits that add the missing `.ncrunchproject` files.

Regards,
Johannes

Hey, thanks for clarifying my suspicions.

Having the whole set of projects available in a single solution has proven to be much nicer than separating this out by task in the past. And since VS (w/o ReSharper) is fairly quick in loading such large solutions there wasn't much need to split this again. Things like quickly trying out different parts of the product require a different set of those sample applications, refactoring needs the whole set, checking whether everything still builds, etc. And since only two people on our team use NCrunch (i.e. value quick test feedback) splitting the solution into different ones is probably not feasible.

But thanks for the answer nonetheless; it was just an idea how I could manage this a bit more effectively. The current approach does work, and there aren't that many new projects appearing, anyway.