Jelle Druyts

This is quite freaky: somewhere in our NUnit tests we declared an int array with two elements to hold some expected results. No problem, tests ran. Now we make it three elements, and NUnit fails to start the test. Using debug mode in the NUnitAddin even gives us an ExecutionEngineException. Poking a little further, it turns out that its even worse: just declaring an int array (and never using it!) of three or more elements makes NUnit turn the other way when you ask it to run the test. Whow. How can that even have any influence? Interception on int[].ctor? This blows my mind.