My hack-ish solution:
I used the MBUnit.Cons.exe in an <exec> task as follows:
<?xml version="1.0" encoding="utf-16"?>
<project default="tests">
  <property name="dll-to-test" value="C:\Visual Studio 2005\Projects
\MBUnitTestProject\MBUnitTestProject\bin\Debug\MBUnitTestProject.dll" /
>
  <target name="tests">
    <exec program="MBUnit.Cons.exe" basedir="C:\Program Files\MBUnit">
      <arg value="${dll-to-test}" />
    </exec>
  </target>
</project>

On Jun 5, 11:20 am, donnieb <[EMAIL PROTECTED]> wrote:
> I'm trying to run my mbunit tests from Nant (version 0.85-rc3), and I
> generated the nant build xml via the GUI tool (MBUnit 2.4.197).
>
> When I run the nant script, I get:
> tests:
>
> C:\Visual Studio 2005\Projects\MBUnitTestProject\MBUnit.build(5,8):
> Element <includes... /> for <fileset... /> is deprecated. Use
> <include> element instead.
>    [mbunit] MbUnit 1.0.2700.29885 test runner
>    [mbunit] Loading 1 assemblies
>    [mbunit]  AssemblyName: C:\Visual Studio 2005\Projects
> \MBUnitTestProject\MBUnitTestProject\bin\Debug\MBUnitTestProject.dll
>
> BUILD FAILED - 0 non-fatal error(s), 1 warning(s)
>
> Unexpected engine error while running Tests
>     Failed loading assemblies
>         Failed loading TestDomain
>             Failed loading assembly
>                 Failed loading test assembly
>
> Total time: 0.2 seconds.
>
> I suspect I may not have copied all the correct files to the Nant bin
> direcotry.  The documentation, considering the structure changes in
> the 2.4 release, is, um, pretty "light" :-)
>
> I get this error whether VS2005 is running or not, so it doesn't
> appear to be an access violation.
>
> Anyone got any ideas?
>
> Don


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to