|
From: Mike R. <mik...@gm...> - 2004-11-03 20:49:29
|
I suggest you do what we do on CCNet and that's to use <exec> . Make
sure that the nunit.framework and nunit.core you're compiling against
are *exactly* the ones you are running with, make sure both
nunit.framework and nunit.core are in the directory of the assembly
you're testing, and make sure you don't have any nunit's installed in
your GAC.
Here's a line from the CCNet build file as an example. I know that
there's properties in it but hopefully you get the picture.
<exec program="${nunit-console.exe}"
workingdir="${build.dir}\core" commandline="${core.dll}
/xml:../${core.dll}-results.xml /nologo"/>
Let me know if you have any more problems.
Mike
On Wed, 3 Nov 2004 09:57:13 -0600, Levi Khatskevitch
<lkh...@th...> wrote:
>
> I'm having a problem with the build script ever since we've moved to NUnit
> 2.2. Here's the error I'm getting:
>
> C:\Work\nmock\nmock.build(39,4):
> Failure executing test(s). If you assembly is not built using NUnit version
> 2.2.0.0, then ensure you have redirected assembly bindings. Consult the
> documentation of the <nunit2> task for more information.
> File or assembly name 'nunit.util, Version=2.2.0.0, Culture=neutral,
> PublicKeyToken=null', or one of its dependencies, was not found.
> The system cannot find the file specified.
>
> If I copy nunit.util.dll into tools directory it works just fine, however
> since this file is already exists in tools\lib\net\1.1 I thought I'd ask if
> anyone else can reproduce the problem before trying to figure it out myself
>
> Thanks,
> - Levi
>
--
mike roberts | http://mikeroberts.thoughtworks.net/ |
http://www.thoughtworks.com/
|