I've found one more serious issue with Rhino.Mocks: if you "Expect" a method call and setup validations on the parameters using Arg<T>.Match(...), this throws an umbiguous method exception. The cause of this is in the implementation of the LambdaConstraint class: it uses reflection to find a method "Compile" for the validation expression and finds more than one "Compile" method.
-- 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/groups/opt_out.
