About once a day, NCrunch seems to get stuck in "build failure" when I either copy&paste some code that introduces source errors, or do some kidns of edits (seem to be associated with introducing use of attributes or something requiring a new using or project dependency). It appears that NCrunch captures the state of the source files in-between when the editing starts (and the code is invalid) and when I have finished (and the code is clean). This only happens a small percentage of the times, but when it does even asking NCrunch to rebuld the failing projects does not work.

I end up disabling/enabling NCrunch to get things working again, but that can be time-consuming.

I cannot repro this on demeand, just something I have noticed. I am using the latest (44) build, but I think I encountered this with earlier builds also, but not frequent enough I sensed a pattern.

Anybody else seeing this?

I get it often when doing Get Latest in Source Control. When a teammate changed a project file, that project has to be reloaded, NCrunch sometimes is not in sync and needs to be reset. Maybe because I have files from that project open at that moment?