|
From: Steve M. <Ste...@ty...> - 2007-11-08 20:33:20
|
I really don't want to maintain two branches, the only real difference is the reference and the 'using' statement for now. So I'll probably just post the changes to my blog and leave the actual code tree alone. -----Original Message----- From: nmo...@li... [mailto:nmo...@li...] On Behalf Of aci...@ac... Sent: Thursday, November 08, 2007 2:25 PM To: NMock2 Development Discussion Subject: Re: [NMock2-Dev] NUnit vs. MbUnit > > While I am of the mind of 'if it isn't broken, don't fix it', I have to > do the work anyway, so... > > > > Would anyone be interested in the move to MbUnit or should I just keep > it internal. > Personally I wouldn't use it, but depending on difficulty maybe we could create a branch/derivation of NMock that uses MbUnit, possibly developing in parallel contributing code and ideas between the two. In this case I think more options make for a better user base and more ideas of how to make NMock2 better. -Richard Holden ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ NMock-two-dev mailing list NMo...@li... https://lists.sourceforge.net/lists/listinfo/nmock-two-dev |