In *.ncrunchsolution paths in MetricsExclusions are absolute - IMHO they should be relative. We keep this file under source control, developers has different paths to their local workspaces, so we are getting conflicts all the time, and this conflicts aren't resolvable.

Another suggestion: MetricsExclusions could have children nodes - one node for file - and this children could be alphabetically sorted. This way automatic confilct resolution will have easier task.

For anyone interested, 1.40b has just been released including the change requested above. Metrics exclusions should now be using relative paths (as opposed to absolute), and are sorted alphabetically for easier merging.

Hi Marqus -

Yes, sorry, I needed to include it as a separate property to simplify the upgrade process (since the file references are now in relative rather than absolute form).

The data is stored at solution level more because of technical/design/ease-of-implementation reasons. NCrunch stores all code coverage information at solution level (i.e. in the .cache file), as the tests that cover a project may not be present in all solutions that use the project.

From a configuration perspective, storing the exclusions at project level does make more sense though. I'll have a think about it.


Cheers,

Remco