Separate ncrhunch project configuration from user setting for source control integration
Currently there is *.NCrunchproject with both user settings and project configuration: what files are to deploy, what build configuration to use, etc...
Once I set up and committed *.ncrunchproject files for 50+ projects, the files continued to change for my local environment: what tests to include, what warnings are disabled, etc...
Idea is to separate Global Configuration from User settings, so we can add *.nchrunchconfig to repository, and *.ncrunchlocalsettings to ignore list.
Now available with the new V3 configuration system.
http://blog.ncrunch.net/post/Announcing-NCrunch-Version-3!.aspx
-
Kit commented
Big for us too (just migrating substantial team to NCrunch as a trial).
-
James Nail commented
This one is big for me too. I've got a few integration test projects that require us to set "Copy referenced assemblies to workspace" (the tests' setups involve conventional IoC registrations which scan referenced DLLs and the bin folder).
Unfortunately, we lose this setting every time we clean our local repos. -
GreenMoose commented
(.user extension is probably more appropriate for user specific settings).