nunit testing 32-bit apps on 64-bit machine

December 28, 2006 · 1 min read

I'm trying to run nunit tests of a 32-bit assembly on a 64-bit machine. When I load the assembly (compiled with VS target platform set to x86) into nunit, I get a FileNotFound exception. The problem is that nunit is running as 64-bit. I found this post by Matevz Gacnik pointing me in the right direction to get around this problem. Here is the fix:

You can use corflags to find out what settings the nunit assembly already has:

C:\> corflags "C:\Program Files (x86)\NUnit-Net-2.0 2.2.9\bin\nunit-console.exe"

Then you can add the 32BIT flag to force it to run as 32-bit:

C:\> corflags "C:\Program Files (x86)\NUnit-Net-2.0 2.2.9\bin\nunit-console.exe" /32BIT+

See also: CorFlags Conversion Tool at MSDN, Explanation of CLR, platform selection, and corflags.

Technorati:,,,

This article is part of the GWB Archives. Original Author: Lance Robinson

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.