The type of the proxy is the same (it is cached) but instances are not. Try doing object.ReferenceEquals(m1,m2) and you'll see.
Tuna Toksöz Eternal sunshine of the open source mind. http://devlicio.us/blogs/tuna_toksoz http://tunatoksoz.com http://twitter.com/tehlike On Thu, Jun 11, 2009 at 7:14 PM, Shane C <[email protected]> wrote: > > Foo currentFoo = MockRepository.GenerateMock<Foo>(); > Foo previousFoo = MockRepository.GenerateMock<Foo>(); > > After executing that code myMockFoo1 and myMockFoo2 both seem to point > to the same proxy instance (or at least mousing over them provides the > exact same ToString() of... > > FooProxy02cb26349447484ca62bb786f3e05044 > FooProxy02cb26349447484ca62bb786f3e05044 > > If this is the case the following expectation doesn't seem trustable.. > > FooService.Expect(mock => mock.ExecuteOn(currentFoo, previousFoo)) > > since the code could be passing 2 first even though the order that > they are passed in IS important to me. In fact based on what I'm > currently working on it appears that the expectation itself never > passes (even when called in the correct order) unless you > IgnoreArguments... > > Thoughts? > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
