I've run into a scenario where I get an InvalidOperationException thrown instead of an ExpectationViolationException. I found the following posting which seems to describe exactly what I'm seeing:
http://groups.google.com/group/rhinomocks/browse_thread/thread/5ae948258cc9251e/7f72bfbbc9b4912c?lnk=gst&q=InvalidOperationException+generic#7f72bfbbc9b4912c. There weren't any responses to it so I was just wondering if it is a known issue that might eventually be fixed or if it is some sort of a design constraint and I should just accept it. The issue I'm having is it is very confusing to members of my team who haven't run across it before. They think something else is wrong besides just missing a method call or having an unexpected one. It would be great to have the normal ExpectationViolationException thrown instead. Thanks, Bryan -- You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhinomocks?hl=en.
