Well, I certainly would! I got around it by "gacutil /i"-ing MbUnit.Framework and every assembly it referenced (like, 4?) to get "It Just Works" functionality rolling, so now I'm fine with it.
Not having to cart a bunch of files (MbUnit and every assembly it references) around per each project file, and instead only referencing MbUnit.Framework, is a definite plus in my opinion. Andrew Stopford wrote: > Hi, > The installer does need improving and this has been raised as a task. > http://www.mertner.com/jira/browse/MBUNIT-21 > I will add some info to the wiki to raise awareness of this until this task > can be closed. > The second you raise, I tend to add referances via VS and let VS do the > heavy work. Of course thats letting the IDE do the work and if your using > another IDE that works in a different manner then I can see this becoming a > pain. I want to cast this out to the group, would you support adding MbUnit > to the GAC as a improvement? > Andy > On 11/13/05, l33ts0n <[EMAIL PROTECTED]> wrote: > > > > > > I was struggling to get Unit Testing support in #develop 2.0 today (via > > the unit tester addin), (http://community.sharpdevelop.net), and > > noticed a few issues with the installer. > > > > First of all there's no feedback: the installer appears to "load," but > > then vanishes. It actually does an installation and everything, but it > > took several minutes of searching (and me launching the installer 2 or > > 3 times) before I realized that it installed MbUnit to my Program Files > > directory. > > > > Second of all, it doesn't register any of its important assemblies to > > the gac, which means cut-and-pasting the relevant DLLs to the target > > directory or registering the assemblies by hand. Both methods suck. ;) > > > >
