BUG: Ambiguous match exception on .Net 4.0 for Arg<>.Matches()

[Xerxesb]

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

[Tim Barcz]

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

--
You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group.
To post to this group, send email to rhino...@googlegroups.com.
To unsubscribe from this group, send email to rhinomocks+...@googlegroups.com.
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

[Xerxesb]

i can give it a shot...Can't guarantee i'll be able to pull anything
off, but sounds like fun ;)

-x

> > rhinomocks+...@googlegroups.com<rhinomocks%2Bunsubscribe@googlegrou ps.com>