nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

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 <rdzikowski@xxxxxxxxx> 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.
>

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

Status in NUnit V2 Test Framework: New

Bug description:
I am using Windows 7 64 bit, Visual Studio 2010, GUI runner, NUnit 2.5.4.10098.

When I compile any program with Build option Platform target set not to Any CPU 
(Platform target is not Any CPU) then I get this exception:

System.IO.FileNotFoundException...

Server stack trace: 
   at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
   at System.Reflection.Assembly.Load(String assemblyString)
   at NUnit.Core.Builders.TestAssemblyBuilder.Load(String path)
   at NUnit.Core.Builders.TestAssemblyBuilder.Build(String assemblyName, Boolean autoSuites)
   at NUnit.Core.Builders.TestAssemblyBuilder.Build(String assemblyName, String testName, Boolean autoSuites)
   at NUnit.Core.TestSuiteBuilder.BuildSingleAssembly(TestPackage package)
   at NUnit.Core.TestSuiteBuilder.Build(TestPackage package)
   at NUnit.Core.SimpleTestRunner.Load(TestPackage package)
   at NUnit.Core.ProxyTestRunner.Load(TestPackage package)
   at NUnit.Core.ProxyTestRunner.Load(TestPackage package)
   at NUnit.Core.RemoteTestRunner.Load(TestPackage package)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at NUnit.Core.TestRunner.Load(TestPackage package)
   at NUnit.Util.TestDomain.Load(TestPackage package)
   at NUnit.Util.TestLoader.LoadTest(String testName)