Hi Daniel,
Thanks for sharing this issue.
I'm not aware of anything in NCrunch that could directly cause this problem. The test environments we create default to full trust, and this looks like the kind of exception that could be thrown from partially trusted or constrained code.
Does this happen consistently for you? Or is it intermittent?
Check that there isn't a virus scanner involved here. They can do some strange things when it comes to security.
Can you try turning off the '
Track File Dependencies' setting? We're aware of some compatibility issues between this and isolated storage.
If you can isolate the issue in a sample project you can share with me (i.e. one that works with other runners but fails under NCrunch), I should be able to investigate further and hopefully provide some kind of resolution.