RE: [Dotnetmock-developer] RE: Merging DotNetMock.Core into DotNetMock

[Choy R. <ch...@rc...>]

Griffin,
 
I made an example MbUnit test project and it worked fine. But I couldn't
get the csUnit stuff to work. It kept resolving the assembly
nunit.framework (or seemed to). If MbUnit is more important, then I'll
leave a note in the csUnit stuff, and we can move on.
 
You don't have to get rid of delayed signing. That's fine. I'll just do
a runas /user:adminuser nant skip-verification, and I'm all good for
running the build + tests. But I just require that sn -Vr target to be
factored out of the build target.
 
I think the next most important thing we need to do is improve our error
messages. I recall Roman has a decent approach. But I'd like to
incorporate his approach into something more complete. Like a complete
review of where we can provide better assertion exception messages in
general. For example, one thing we should flag is all uses of
Assertion.Assert* methods that DON'T take a message argument (perhaps
outlaw it).
 
Although that "expectation path" stuff is cooler, better assertion
messages will improve my day to day TDD a lot more. A whole lot more.
 
--Choy
 
 
 
-----Original Message-----
From: Griffin Caprio [mailto:gri...@ma...] 
Sent: Tuesday, February 01, 2005 12:37 PM
To: 'Choy Rim'
Cc: dot...@li...
Subject: RE: [Dotnetmock-developer] RE: Merging DotNetMock.Core into
DotNetMock
 
Choy,
 
Awesome.  I saw that.  I am going to remove the old *Namespace dll's
from the main distro then.
 
I program as admin ( I know, I know... ;) ), so maybe this is something
that only admins can do.  I will figure out a way to integrate the
strong name into development.  Sorry for the inconvenience.
 
I will look into the MbUnit & csUnit support this week.  I will
concentrate on MbUnit, since csUnit appears to be abandoned.
 
Great, I after all of this, I will prep a release.  Then we can look
into Roman's stuff more closely to see what should be merged in.
 
Thanks,
 
Griffin
 
  _____  

From: Choy Rim [mailto:ch...@rc...] 
Sent: Saturday, January 29, 2005 3:26 AM
To: 'Griffin Caprio'
Cc: dot...@li...
Subject: RE: [Dotnetmock-developer] RE: Merging DotNetMock.Core into
DotNetMock
Griffin,
 
I've done the merge.
 
I had a little trouble with the sn -Vr stuff in the build target. I
pulled it out into a separate "skip-verification" target so that I could
run it separately under an admin account. I don't normally develop under
an admin account. Hopefully this is ok.
 
I don't use MbUnit or csUnit so I not quite qualified to verify that the
dynamic test framework binding works. I was wondering if you could
verify at least one of them. A more comprehensive approach would be to
make several example test projects, one for each framework. But that
would take a while. I'm quite confident about how it will work for NUnit
. but for the other two I can't be sure.
 
Otherwise, I'll be off trying to see how to merge some of Roman's stuff.
 
--Choy
 
 
 
-----Original Message-----
From: dot...@li...
[mailto:dot...@li...] On Behalf Of
Griffin Caprio
Sent: Thursday, January 27, 2005 3:16 PM
To: dot...@li...
Subject: [Dotnetmock-developer] RE: Merging DotNetMock.Core into
DotNetMock
 
Choy,
 
Ok, sounds good.  If you don't have time, I can do it tonight.  I don't
have a problem with that.  I would like to get a release out this
weekend, as we have a couple of "cleanup" bugs going out, like being
able to support NUnit 2.2 & signing the assemblies.
 
-Griffin
 
  _____  

From: Choy Rim [mailto:ch...@rc...] 
Sent: Thursday, January 27, 2005 12:46 AM
To: 'Griffin Caprio'
Cc: dot...@li...
Subject: RE: Merging DotNetMock.Core into DotNetMock
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