Rhino MocksUndebuggable

time to read 2 min | 243 words

“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.” – Brian W. Kernighan

Apperantly I am not smart enough to debug Rhino Mocks. Here is what I get when I try to debug Rhino Mocks in Visual Studio 2005 SP1. The really sad part is that SharpDevelop can debug the code without an issue.

(Image from clipboard).png

> oleaut32.dll!77d03c34()  
  [Frames below may be incorrect and/or missing, no symbols loaded for oleaut32.dll] 

More posts in "Rhino Mocks" series:

  1. (30 Jun 2008) Getting closer to conclusion
  2. (29 Jun 2008) The role of Stub vs. Mock
  3. (29 Jun 2008) To be strict or not?