Hi, The genertion code for the MSBuild generation may be broken. What I would try is to run MbUnit via the console msbuild task first, if that works out ok then try the msbuild task (coding by hand first).
Andy On 4/27/07, AC [MVP MOSS] <[EMAIL PROTECTED]> wrote: > > > I have been running my unit tests with the GUI, but want to integrate > it into my build process. Before I add the complexity of CC.NET, I > wanted to just add the custom MSBuild task that the GUI generates to > my project file and have it run when I compile in DEBUG mode. I then > added a CallTarget pointing to the MbUnit target within the AfterBuild > target. > > After adding the XML generated by the GUI, I made one change: set the > full path to the assembly containing the custom MSBuild task for > MbUnit. However, I keep throwing errors left and right: > > C:\Development\MyProjects\CR_SPUtilities\trunk\CR_SPUtilities > \UnitTests\UnitTests.csproj(78,5): error : Unexpected failure during > MbUnit execution > C:\Development\MyProjects\CR_SPUtilities\trunk\CR_SPUtilities > \UnitTests\UnitTests.csproj(78,5): error : Failed loading assemblies > C:\Development\MyProjects\CR_SPUtilities\trunk\CR_SPUtilities > \UnitTests\UnitTests.csproj(78,5): error : at > MbUnit.Core.Graph.TestDomainDependencyGraph.BuildGraph(String[] > testAssemblies, String[] assemblyPaths, IFixtureFilter fixtureFilter, > IRunPipeFilter runPipeFilter, Boolean verbose) > C:\Development\MyProjects\CR_SPUtilities\trunk\CR_SPUtilities > \UnitTests\UnitTests.csproj(78,5): error : at > MbUnit.Core.Graph.TestDomainDependencyGraph.BuildGraph(String[] > testAssemblies, String[] assemblyPaths, IFixtureFilter fixtureFilter, > Boolean verbose) > C:\Development\MyProjects\CR_SPUtilities\trunk\CR_SPUtilities > \UnitTests\UnitTests.csproj(78,5): error : at > MbUnit.MSBuild.Tasks.MbUnit.InternalExecute() > C:\Development\MyProjects\CR_SPUtilities\trunk\CR_SPUtilities > \UnitTests\UnitTests.csproj(78,5): error : at > MbUnit.MSBuild.Tasks.MbUnit.Execute() > > This happens just after the "Verifying report names" message in the > output window. I can see the MbUnit target firing off, just fails in > the middle. Ideas? > > Ideas? > > -AC > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
