Ayende @ Rahienhttp://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Judah commented on Planning Rhino Mock 3.5 - The Lambda EditionI agree with Krzysztof, better support for events would be great. http://ayende.com/3154/planning-rhino-mock-3-5-the-lambda-edition#comment3http://ayende.com/3154/planning-rhino-mock-3-5-the-lambda-edition#comment3Wed, 20 Feb 2008 15:01:37 GMTKrzysztof Koźmic commented on Planning Rhino Mock 3.5 - The Lambda EditionContrats on 3.4 release. I'd love to see easier support for event handlers. Something like what I described on my blog here: http://kozmic.pl/archive/2008/02/15/testing-callbacks-with-rhino.mocks.aspx http://ayende.com/3154/planning-rhino-mock-3-5-the-lambda-edition#comment2http://ayende.com/3154/planning-rhino-mock-3-5-the-lambda-edition#comment2Mon, 18 Feb 2008 13:02:11 GMTJon Skeet commented on Planning Rhino Mock 3.5 - The Lambda EditionI guess the most obvious one is argument or return validation, taking a Func<T,bool>. If you wanted to be able to log the constraint being violated (and you're in the .NET 3.5 world) you could take an Expression<Func<T,bool>>, compile it to actually run it, and log the ToString() form in case of a violation. I'm sure there'll be more stuff though - next time I'm doing any reasonably complicated mocking I'll see what I can find :) (Another option might be to use it to respond to methods, if you needed more behaviour than just returning a constant value.) http://ayende.com/3154/planning-rhino-mock-3-5-the-lambda-edition#comment1http://ayende.com/3154/planning-rhino-mock-3-5-the-lambda-edition#comment1Mon, 18 Feb 2008 11:36:55 GMT