Moq/moq4 — pull request #8 by srudin (2012-06-06 11:38:48+00:00)
Title: CallBase() / Throws() within SetupSequence / Solution fixes

Hello

I have implemented two features and fixed a couple of (minor) bugs:

First I added the option to be able to call the base (original) method for a specific setup – here’s a link where someone else has discussed this request: http://code.google.com/p/moq/issues/detail?id=293

Second I added the option that either Throw() or CallBase() is available within a setup sequence chain – again here’s a link where someone else has discussed this request: http://code.google.com/p/moq/issues/detail?id=319

Finally I adjusted the references in the UnitTest project to match those of the Moq project (I had compiler errors without that fix). I also adjusted the command line for merging the castle library into the moq library because the way it is specified now it will always compile for .NET runtime 4.0 even when the project is set to 3.5 and the 2.0 runtime should be used. And I added a .gitignore because I got tired of all the temp files being listed in my Commit dialogue.

I think the changeset is rather small and self explinatory but I admit that I’m not sure whether all my changes are implemented the best way (kind of tricky to keep the overview over all the interfaces) so maybe improvements are possible? Just get back to me if I can be of any help.

Thanks & kind regards
Sandro