Agreed, we can add it to the field problems once we have more context. Just from looking at the problem, however, I can't tell if there was a typo or not but the only thing that is being mocked is the IDbConnection rather than the decorator. Therefore, getting an actual unit test to look at would help clear that up and provide context.
Just for kicks, I would setup the mock as a Strict Mock. That way if anything is called that wasn't expected you will know. You could also try using a logger to get a better understanding of what is being called and what Rhino Mocks is doing. Hope that helps -- You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rhinomocks. For more options, visit https://groups.google.com/d/optout.
