Hi,

I just tried the debug test feature of 1.37b for the first time (little need to debug otherwise). I noticed that the Debug 'Autos' and 'Locals' have some odd key/values in them. Not the local variables one would expect while debugging. I noticed that while in a the 'item' variable is not known. I was also using some linq and aunonymous types and these were also not available (no debugging tooltips etc.)
Perhaps this is due to the way that you start up the debugging session?
As it is obviously a lot faster to start debugging this way (;-)

I'm getting these results in iterator blocks (methods with `yield return` in them).

I've had a good look at this issue in depth, and it seems to be caused by a mismatch between the expectations of the VS debugger and the structure of the code under test.

It appears that Visual Studio has been programmed with some kind of algorithm that infers the local variables of the 'yield return' method by analysing the structure of the generated iterator block. Since the local variables in a 'yield return' method aren't actually variables (they are in fact fields on a nested class generated by the compiler), this is extremely useful for normal situations as otherwise you simply wouldn't be able to see any values at all.

NCrunch needs to manipulate the structure of the generated iterator block in order to perform coverage analysis, and by doing so it changes what the Visual Studio debugger 'sees' in the code and the inference algorithm fails.

Sadly I see no way of easily solving this problem from the side of NCrunch, as the manipulation of the output assembly is required for code coverage analysis. It's highly likely I won't be able to fix this problem in the immediate future.