(Minor) NCrunch leaves redundant files when renaming projects/solutions

I've noticed that when I rename a project or solution, ncrunch will create new settings files (e.g. the .ncrunchproject file), but not delete the old ones. Also, I sometimes need to re-enable ncrunch when I re-open the solution.

Thanks for reporting this - I'll note it down for fix. Can you provide some more details around what happens with the engine before you need to re-enable it? Is it just that it doesn't enable itself? Or does it bug out?

Remco wrote:Thanks for reporting this - I'll note it down for fix. Can you provide some more details around what happens with the engine before you need to re-enable it? Is it just that it doesn't enable itself? Or does it bug out?

It just didn't enable itself, and I had to go through the enabling wizard again.

My suspicion is that when this happens for you, the reason is probably because NCrunch wasn't able to access the .ncrunchsolution file for your solution. This file contains a property called AutoEnableOnStartup, which is set whenever you enable or disable NCrunch. Is it possible that you have this file locked somehow? Perhaps using a read-only flag?

If NCrunch is losing other settings too, there may be something more catastrophic going on (i.e. source control system nuking the config files). Let me know if you manage to find a clear pattern that causes the problem, and I'll try to help you analyse it.

For anyone interested, a fix for the above problem (rename of projects) has been introduced with the newly released version of NCrunch (v1.45).