I don't have a sable 4.0 box going yet (other than transient VM's). Any chance you'd want to take a stab at fixing it?
Tim On Sun, Jan 31, 2010 at 6:14 PM, Xerxesb <[email protected]> wrote: > Hi there, > > I found a topic in the group from back in May 2009 identifying this > bug, but it doesn't appear to have been resolved (and the discussion > appears closed) > > I'm still having the same problem with a 4.0 targeted assembly failing > with the simple following case: > > public interface IFoo > { > string DoFoo(string foo); > } > > public class Bar > { > public void DoFoo(IFoo foo) > { > foo.DoFoo("some string"); > } > } > > public class TestClass > { > [Test] > public void TestBlah() > { > var mock = MockRepository.GenerateMock<IFoo>(); > > new Bar().DoFoo(mock); > > mock.AssertWasCalled(x => x.DoFoo(Arg<string>.Matches(obj > => true))); > } > } > > > Any plans to have this fixed in Rhino soon? > > Cheers, > Xerxes > > -- > 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]<rhinomocks%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rhinomocks?hl=en. > > -- Tim Barcz Microsoft C# MVP Microsoft ASPInsider http://timbarcz.devlicio.us http://www.twitter.com/timbarcz -- 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.
