Hello! This couldn't be more of a newbie MbUnit question, so just a heads up. :)
I've installed the latest MbUnit (2.4.x) on my machine. I've inherited a very large hierarchy of code in .NET projects (using .NET 2.0.x) that has already integrated MbUnit.AddIn and MbUnit.Framework. In fact, there is a project created for the sole purpose of being run by MbUnit GUI so that our team can see unit test reports at will. This latter project is the one I'm currently trying to generate a report from in the MbUnit GUI, but I'm having fundamental problems making it work. I can generate reports inside the .NET project itself without problems. However, the performance is much slower within .NET than in the GUI. I've hit a major problem trying to get the .NET project to work in the GUI. Essentially, I have to copy my assembly into the MbUnit install directory, directly -- alongside all of the assembly's dependencies. Once I get the test to run, every test fails because of a TypeInitializationException. This is (I gather) due to the assemblies being forced into a flat directory and, hence, are missing the hierarchy necessary for them to run. Is there a way I can supply a list of paths for which the MbUnit GUI can accept such that the app can still reference its own DLLs while being able to load an assembly in a foreign directory tree? Brian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
