Hi, thanks for posting.
I'm not aware of anything in NCrunch that would specifically cause this problem. It's possible that NCrunch is surfacing the issue indirectly, or that you've discovered something unusual between the multiple toolsets in use here (NCrunch/MSBuild/FSharp/NUnit).
I think it may be worth trying to place your NCrunch in
compatibility mode to see if this makes any difference.
Do you experience this problem when attempting to run your tests directly using NUnit? (i.e. the NUnit GUI or console runner). Note that TestDriven.NET isn't always the same as these.
If you can submit a buildable/runnable code sample that I can play with, I should be able to help find the problem very quickly. You can submit code via the
contact form.
Thanks!
Remco