Typesafe, refactoring resilient Mock.ExpectedCall

I just wrote a post on my blog experimenting with an implementation of an extension method for the Mock.ExpectedCall() method which is 100% typesafe (my primary goal was to make it resilient to method name refactorings), by using a trick the ASP.NET MVC framework has pioneered. It uses lambda syntax and evaluates it as an expression tree to pick out the method name, and looks like this in use:

Mock fooMock = MockManager.Mock<Foo>();
fooMock.ExpectCall<Foo>(f => f.Bar());

It does have a few limitations (only works for public non-static methods), but I think it has the potential to be a very useful feature, especially for those who don't have the Pro/Enterprise editions with Natural Mocks :wink:

Similar overloads could be implemented for several other Mock members aswell.

You can find a detailed discussion + source code for the extension method on my blog :)