.Net, Rhino Mocks

Unwinding Rhino Mocks

Finally, progress!. Sure, the “progress” is 124 build errors but… it’s progress; right?

One of the things that I have been doing is cleaning up the code base by removing projects, assemblies and code that are no longer relevant. I am actually surprised of how much code was never built. It has also been interesting finding artifacts from previous build strategies and repositories. Things like NAnt scripts and merge diff files (from SVN). Even found an old version of NUnit hiding out.

To be honest, this is some of the most fun that I have had in a while. There is nothing better than deleting things!
(Perhaps I need to get out more)

Attempting to update to the latest version of Castle Dynamic Proxy (now in Castle.Core assembly), however, has caused a little problem. About 124 problems to be exact. Armed with my trusty editor (Vim), these issues have been quickly dispatched.

With the build errors fixed there are now nine tests failing (out of 806). Progress indeed. Hopefully these will be corrected tomorrow so I can commit the changes and start digging into some “real” changes.

Advertisements
Standard

2 thoughts on “Unwinding Rhino Mocks

  1. Pingback: Dew Drop – June 7, 2013 (#1,563) | Alvin Ashcraft's Morning Dew

  2. Lauren says:

    If cleaning and purging is the most fun you’ve had in a while…. getting out more might help. But it does sound like good progress. What “real” changes are you contemplating?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s