distilled;15311 wrote:
Yep, I can confirm that that's what I'm seeing. I guess in my experience the file hash very rarely matches what NCrunch has cached, and most of the time when I launch VS I need to quickly disable NCrunch or tell it to ignore everything so that it doesn't try to start running all of the tests.
The hashing system is very sensitive to even the smallest of IL changes in the code. If you regularly update from a VCS before opening your codebase, you'll likely see tests get triggered every time a changeset comes down. If you have a lot of long running tests that NCrunch is running a bit too eagerly, you might want to consider setting up your own engine mode that separates them out to be executed manually.