-
Website
http://blog.ashmind.com/ -
Original page
http://blog.ashmind.com/index.php/2007/09/23/nmock-35/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
regisbsb
3 comments · 1 points
-
Busby SEO Test
1 comment · 1 points
-
Weex
1 comment · 2 points
-
alwin
1 comment · 2 points
-
ctacke
1 comment · 1 points
-
-
Popular Threads
Would you please send me copy of the code?
Thanks.
Mine is ashmind+blog(at)gmail.com.
Nice one! I had a slightly different approach though (scroll downto "Improvements: NMock2 + C#3." at http://codevanced.net/post/Touching-a-hot-iron-... )
I have moved to Moq and it saved me from writing a whole new API for NMock2 just to get more modern syntax.
Also Moq people were very responsive at fixing bugs when they still had them.
I wish I could say the same about latest NMock2.
Latest release appears to be of December 06 2008 at sourceforge, and SVN statistics ( http://sourceforge.net/project/stats/detail.php... ) shows some checkins :)
Why do you think it's "dead for a while"?
I am subscribed to their newsgroup and there was only occasional activity for almost a year (consistent with no releases for a while).
It seems that they started releasing and the discussions moved elsewhere so that's the reason for my error.
However unless they already support .NET 3.5 syntax, it still seems for me that MoQ is easier to use for NET 3.5 projects.
The reason is that the developers of NMock version 1.0 and 2.0 (nmock.org) have stopped their development and it is continued by another team on http://sourceforge.net/projects/nmock2/
Back to lambdas:
Do you have a solution that supports defining expectations on properties and indexers as well?
Happy mocking
Urs