Hi Eric,
Funny really I have just fixed this but our SVN server has gone pear shaped so I can't commit the change. In the mean time you can get around this by editing your MbUnit.GUI.Config file in your program files\MbUnit folder. You will need edit this and add
v2.0.50727, for my own purposes I commented out 1.0 and 1.1 and this will make MbUnit GUI switch to 2.0. I have enclosed a copy of the config file if you need it, be aware that this change will be in the next build.
The reason MbUnit GUI is giving this error is that you trying to load a test compiled in 2.0 into MbUnit GUI which is in 1.0 mode. I think in the future MbUnit GUI and MbUnit console will default to 2.0.
Glad your using the latest build :)
Thanks
Andy
On 11/22/05, ehahn9 <[EMAIL PROTECTED]> wrote:
Alas, my mileage seems to vary :-(
When I use build 2.3.0, the caption says " 2.3.0.0 (on .Net 1.0.5000.0)"
- is this right?
When I try to load even the most trivial test .dll (3 xxxTest methods)
into the GUI, I get this exception:
System.ApplicationException: Failed Reloading domain --->
System.ApplicationException: Failed loading TestDomain --->
System.Exception: Failed loading assembly --->
System.BadImageFormatException: The format of the file
'MbUnit.Framework' is invalid.
File name: " MbUnit.Framework"
I guess I don't understand how MbUnit.Gui.Exe, bound to 1.0.5000, could
ever parse a DLL created by the 2.0 compiler... But this seems to be
complaining about the MbUnit.Framework itself -- odd? Might I somehow
be getting an old MbUnit.Framework.dll (I checked the GAC, nothing
there).
Do I need to somehow redirect MbUnit's .Net version in the .config file
to force MbUnit.gui.exe to pick up the 2.0 runtime?
Thanks for your patience, Andy! I really appreciate the assistance.
-Eric
MbUnit.GUI.exe.config
Description: application/xml
