I’m in the early stages of a new project with the dashing and debonair Brian Donahue. On the plus side, despite his misgivings, the codebase is in pretty phenomenal shape all things considered. SVN repository, automated build and tests, ActiveRecord, views reasonably separated into MVP. Even a half-finished CI process which is impressive for a one-man team. Like any codebase, it has its share of issues but all in all, I won’t be using this as a sample app for a brownfield application.
On the minus side, he reads my blog so I’ll have to be more subtle in the digs I make toward my workplace.
Anyway, one of the first things I like to do when I start looking through a steaming pile of excrement that someone calls "codebase" is check out the warnings that are lingering. The code had its share with the vast majority related to an upgrade to the latest version of Rhino Mocks but without changing CreateMock. This was an easy fix as a global search and replace from CreateMock to StrictMock got rid of over 80% of the errors.
The rest were a flurry of ReSharper refactorings until I got to the final four. Four assemblies reported the error: found conflicts between different versions of the same dependent assembly.
Double-clicking this error gives a helpful message offering to add a binding section to the assemblies app.config file. I say helpful seriously there because, while I had no intention of keeping that section in the app.config, at least it was able to tell me what the error message couldn’t. Namely, which assembly was causing conflicts.
Or so I thought. The new app.config section seemed to indicate that there were NHibernate conflicts among various projects when I knew for a fact that we had exactly one copy of the NHibernate dll in the entire project.
Here’s where Reflector comes in. More specifically, here’s where it’s extensibility comes in. Through the use of the Assembly Graph add-in, I was able to generate a picture of the dependencies. (Click on the image to the right for a bigger version.) As you can see, all referenes to NHibernate are going to the same assembly.
But as you can also see, there are three semi-related assemblies that aren’t being referenced at all. Which means they can safely be removed from the various projects, yesno?
You probably think that’s foreshadowing’s cooler cousin, foreboding, but it’s not. The answer is yes, I was able to remove them with no ill effects.
The reason I know there are no ill effects? Unit tests, baby! None o’ this "let’s take a stroll through the application and see if it still works" nonsense for me*. Remove the reference, run through the build process and watch the magic happen.
The reason this is important: I’m pretty sure this add-in doesn’t account for dynamically loaded assemblies. And while I’m also pretty sure we would have no reason to dynamically load some peripheral NHibernate assemblies, it’s nice to have a suite of unit tests backing up that assertion.
So to re-cap:
- Unit tests good
- Automated builds good
- Reflector good
- Assembly Graph add-in good
- Subversion good (I haven’t provided explicit evidence of this here but it’s worth mentioning.)
Kyle the Reflectively Assembled
*Brian, if you’re reading, I’m lying. I did actually go through each section and make sure it’s working. But back me up if anyone asks.