Re: [NMock2-Dev] Consolidation of NMock and NMock2

[Thomas W. <tho...@gm...>]

Hi Steve

Thanks for your reply.

I do not understand "...how far you've taken the syntax away from 
NMock2's style.". One of our goals was to have full backward 
compatibility to the original NMock2 project. To prove this, I opened an 
older project that we started 3 years ago with NMock2 version 1.0. The 
project compiled immediatly **without any** modification. 15 of the 242 
tests failed because of the new mock generation and some missing return 
values.

I think we did a great job in backward compatibility and we had a lot of 
discussions about it. I always fought for the full compatibility! And 
the current release candidate published on the sourceforge site provides 
the ability to mock classes too!

You can compare your "old" syntax
     http://nmock.org/cheatsheet.html
with the new one here:
     http://nmock2.sourceforge.net/doc/NMock2-Cheat-Sheet.pdf

As I always said, our goal is to **continue your great work** and we are 
still confident about the simple NMock2 syntax. My concern is that users 
are confused when they browse to the nmock project site. Just forward 
them to the nmock2 project site.

Cheers
Thomas

On 18.02.2009 22:51, Steve Mitcham wrote:
> ...
> My big concern is with how far you've taken the syntax away from NMock2's style.  Granted, for .NET 3.5 there is a need to move away from the existing style,  however, I wouldn't want users of the project to think that they are getting an upgrade to what they have, only to discover that it is actually quite different.  So if you start consolidating, it would be nice to have a migration guide ready as well as your code drop.
> ...
>