It seems like .net 4 does not like the Arg<T> syntax in Rhino.Mocks.
Which is really bad since I really fancy the syntax.
Below is a sampe of the syntax I've used for converting from the
Arg<T>
Func<CallRequestDTO, bool> checkArgs = dto =>
dto.TermDateRow.TermDateID == this.termDateRow.TermDateID;
this.putCallServiceMock.AssertWasCalled(m =>
m.getCallPossibleDocument(null), option =>
option.Callback(checkArgs));
On AssertWasCalled the syntax does the job, not as good as Arg<T>. But
it is suffiencient until we decide what to do with Rhino.Mocks
and .net 4.
When it comes to where we have used Expect and Arg<T>, I fail to find
a good replacement for the Arg<T> syntax.
Any suggestion?
Best regards
Stian
--
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.
