Quote:So it was triggered by a config change that was introduced to work around a different issue.
Yes.
Quote:There is something unusual in the way your assembly references are working. I haven't seen instrumentation cause this kind of problem before, since it doesn't tamper with the references themselves. I would be interested to know why turning off prevent signing of assembly was needed here.
This became necessary because this assembly needed access to protected resources, and such access is only possible from signed assemblies.
Quote:I think there's a likelihood that the runtime problem you're getting is related to the same core issue, and by turning off instrumentation it's just been pushed downstream.
I don't think so, I rolled the code back to a state where this access was not yet required, and even there the previously described configuration change leads to an error.
What’s strange is that NCrunch needs to be restarted to see a change in behavior and old (working) Configuration is without <Setting> tag. Is it same as an an Empty configuration?
Quote:If you set your Log Verbosity to Detailed and examine the log for the failed test run inside the Processing Queue Window, do you get more exception details?
I didn’t notice anything suspicious. I send you logs of working/failing Build/Analyse Tasks per Suport form with the same name as a Topic here.
