You do not have to add it manually. You simply reference the DLL. I don't see what could be simpler. Not having to register things somewhere is a benefit of .NET, IMHO.
A possibly related problem, however, is that Visual Studio always gives errors because it's trying to debug into MbUnit. I'm guess this is either because it's not in the GAC, or because it's compiled with debug symbols. I will try to investigate further. While I eventually just got used to it, I'm hearing the frustration of other developers at my company who I'm trying to get to use MbUnit. Of course there are enough extra screen in the installer now to have a "register in GAC" optional checkbox. (As an aside, I recently read Jef Raskin's _The Humane Interface_ and following his ideas of information efficiency, the old installer that just installs when run [which could be improved with a progress bar that fades away when done] is infinitely more efficient than adding the Next, Next, Finish sequence. But this is not the MbInstaller project so I won't try to change the industry "best" practices on that here.) Thanks, Marc
