From: Choy R. <ch...@rc...> - 2005-01-27 06:45:45
|
Griffin, Sounds great. I'll merge the branch pretty soon (like in a day or so). I'd like to take all the ITestFramework implementation resolution code out of Assertion and somewhere inside the DotNetMock.TestFramework namespace. But if I don't have enough time, I'll just merge it in, and clean it up in the trunk. --Choy -----Original Message----- From: Griffin Caprio [mailto:gri...@ma...] Sent: Wednesday, January 26, 2005 11:28 PM To: Choy Rim Cc: dot...@li... Subject: Re: Merging DotNetMock.Core into DotNetMock Choy, I have no problem doing this. Also, I looked over your RFE branch. It looks great. When would you like to merge it back into the head? After that, I will merge the two projects, then purge what we don't need. Sound good? Griffin http://blog.griffincaprio.com On Jan 26, 2005, at 12:14 AM, Choy Rim wrote: Griffin, I was wondering if you'd consider merging DotNetMock.Core into DotNetMock. DotNetMock.Core only has ITestFramework in it. Although that means that our test framework implementation assemblies now depend on all of DotNetMock instead of just a single interface, it simplifies things for users. In fact, I'd like to deploy just one assembly for everything but that's too much change at once. This is a relatively small change and it does simplify the user experience quite a bit. It would make it easier for me to explain to others what they need to use DotNetMock. --Choy |