In that case, if you are debugging an x-86 program on a 64-bit OS, you
_will_ see the error.
NUnit.exe is IL only and therefore runs as 64 bit on an 64-bit OS.
NUnit-x86 is provided to
take care of this problem.
However, I would not expect to see this particular problem when
testing an x-64 target.
It sounds like you are also having the additional problem with .NET
4.0 that was discussed
in two separate bugs. The 2.5.4 NUnit release will not run tests under
the final release
(or the RC) of .NET 4.0 unless you force nunit itself to run under
that release. This is
already fixed in 2.5.5, which I will be releasing this week.
Charlie
On Tue, Apr 20, 2010 at 6:57 AM, Robert Dzikowski <email address hidden> wrote:
> I run nunit.exe
>
> --
> System.IO.FileNotFoundException when Platform target is not Any CPU
> https://bugs.launchpad.net/bugs/566907
> You received this bug notification because you are a member of NUnit
> Developers, which is subscribed to NUnit V2.
>
In that case, if you are debugging an x-86 program on a 64-bit OS, you
_will_ see the error.
NUnit.exe is IL only and therefore runs as 64 bit on an 64-bit OS.
NUnit-x86 is provided to
take care of this problem.
However, I would not expect to see this particular problem when
testing an x-64 target.
It sounds like you are also having the additional problem with .NET
4.0 that was discussed
in two separate bugs. The 2.5.4 NUnit release will not run tests under
the final release
(or the RC) of .NET 4.0 unless you force nunit itself to run under
that release. This is
already fixed in 2.5.5, which I will be releasing this week.
Charlie
On Tue, Apr 20, 2010 at 6:57 AM, Robert Dzikowski <email address hidden> wrote: IO.FileNotFound Exception when Platform target is not Any CPU /bugs.launchpad .net/bugs/ 566907
> I run nunit.exe
>
> --
> System.
> https:/
> You received this bug notification because you are a member of NUnit
> Developers, which is subscribed to NUnit V2.
>