Bit of a showstopper for me, this. I've got 700 tests using a dynamic type but with the var keyword. Builds fine in VS and MonoDevelop, but not in NCrunch, which is treating the "dynamic" as "object". I suspect this is a known issue, but until it's fixed, I can't use NCrunch.

Mark's talking about his Simple.Web project.

The git repository is: https://github.com/markrendle/Simple.Web.git

I've just given this solution a spin. Unfortunately it didn't produce the problem described (all tests passed for me with one exception, which looked like an unrelated issue). I wonder if there may be something about this issue that's system related. Graeme - does the issue also occur for you?

Hi Mark,

Thanks for posting the link to your solution. With this information, I've been able to isolate the issue and I can confirm that a fix will be in the 1.40b release due out in a few days time. Meanwhile I can suggest a couple of workarounds:

1. Add a parameter to each of the problematic methods that are returning a dynamic type. The parameter can be completely unused, but it will cause NCrunch's instrumention to work along a different code path and will prevent it from corrupting the assembly.
2. Turn off the NCrunch 'Instrument Output Assembly' configuration option for any projects containing problematic methods. This will also disable code coverage reporting for these projects.

It's somewhat surprising for me that this issue has existed for so long. I guess not too many people are writing parameterless methods that return dynamic types across assembly boundaries.


Cheers,

Remco

For anyone interested, 1.40b has just been released including a fix for the above issue. Thanks again for the help in examining this problem.