I'm wondering if anyone has specific details on how to make the current MbUnit MSI's work in a .Net 2.0 environment? I can't seem to avoid geting BadImageFormat exceptions when loading a 2.0 assembly.
I spent a few hours recompiling MbUnit onto 2.0 (actually 2.0.50727) natively, with mixed results. The good news is that a 2.0-built MbUnit can indeed run 2.0-built test fixtures! The bad news is that getting the compile to work was nasty and I probably made many errors, but here are some of the things I discovered: 1. If you you MSBuild, you'll need the 1.0 and 1.1 dotnetfx redists on your build machine. If you compile in the IDE, you won't. 2. There are some version-specific references to down-rev GAC entries - for example, System.web - probably should clean those up. 3. The GUI contains an explicit include of MbUnit.GUI.exe.config in the files list, but when placed in the bin/Debug output directory, will cause vshost to throw exceptions - I just removed it from the project and things worked fine. Anyway, if a pre-built 2.0 MSI isn't in the works, I'm wondering if anyone with more experience with the MbUnit build tree could help perfect a "build onto 2.0" howto? Thanks! MbUnit is so far beyond VSTS 2005's unit test mechanisms (which are basically NUnit-level) that I think it may continue to be popular for the thoughtful developers out there otherwise using VSTS.
