NUnit on Whidbey Beta 1 experiences…


I’ve been having problems getting NUnit to work on Whidbey Beta 1, and I’m curious what experiences you’ve had, either good or bad. Jim hasn’t been having the same trouble, so we’re trying to figure out what’s what. For him, it works if he updates the config file, but I’m getting a BadImageFormatException.

Comments (8)

  1. Randy Ridge says:

    I found that by reordering the supportedRuntime node in the GUI config such that the 2.0 node came before the others fixed issues with BadImageFormatException.

  2. Dono says:

    You linked to James’ blog, but did you see this specific post?

    http://weblogs.asp.net/jamesnewkirk/archive/2004/07/05/173513.aspx

    I had the same problem until I followed his instructions. As per his instructions, I only have

    <startup>

    <requiredRuntime version="v2.0.40607" />

    </startup>

    in the .config files. No other runtimes are listed.

  3. Sam Gentile says:

    As long as you list the 2.o required runtime first, it works. I have verified this on various machines

  4. Josh Jonte says:

    I get a "different thread tried to modify the label lblXXX" exception if i make NUnit the startup project (when i press play), however, if i just attach to the NUnit process to debug …all is right with the world.

    To rememdy this i thought "i’ll just build NUnit in Whidbey"…that didn’t go so well.

  5. MBA says:

    Helpful For MBA Fans.