I have looked around at all the different issues regarding these two. Most of them seem pretty old, so I don't know if they still apply.
Right now I am trying to implement MbUnit as part of Continuous Integration using CruiseControl.Net. I have tried the different "tricks" to solve this problem. I have moved MbUnit.Framework.dll, QuickGraph.dll, QuickGraph.Algorithms.dll, TestFu.dll and Refly.dll assemblies into the .net 2.0 folder and I have put them into the bin folder with my test dll. This is the current error I am getting: C:\sandbox\BuildForge\CodeSmithTools\Feedback\trunk \Master.proj(56,10): error : Unexpected failure during MbUnit execution C:\sandbox\BuildForge\CodeSmithTools\Feedback\trunk \Master.proj(56,10): error : No assembly to test C:\sandbox\BuildForge\CodeSmithTools\Feedback\trunk \Master.proj(56,10): error : at MbUnit.Core.Graph.TestDomainDependencyGraph.BuildGraph(String[] testAssemb lies, String[] assemblyPaths, IFixtureFilter fixtureFilter, IRunPipeFilter runPi peFilter, Boolean verbose) C:\sandbox\BuildForge\CodeSmithTools\Feedback\trunk \Master.proj(56,10): error : at MbUnit.Core.Graph.TestDomainDependencyGraph.BuildGraph(String[] testAssemb lies, String[] assemblyPaths, IFixtureFilter fixtureFilter, Boolean verbose) C:\sandbox\BuildForge\CodeSmithTools\Feedback\trunk \Master.proj(56,10): error : at MbUnit.MSBuild.Tasks.MbUnit.InternalExecute() C:\sandbox\BuildForge\CodeSmithTools\Feedback\trunk \Master.proj(56,10): error : at MbUnit.MSBuild.Tasks.MbUnit.Execute() If I use the MbUnit gui to add the assembly, it will execute the tests just fine. Any Ideas? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
