Comment 22 for bug 582051

I have a few comments to add (apologies if I missed anyone else mentioning these above...)

To quote Carlos S, "I am having the same problem with VS 2010, .NET 4.0, NUnit 2.5.5.10112 on a 64 bit system."

My testing project worked fine under .NET 3.5, with NUnit 2.5, even on this 64-bit machine.

After upgrading (.NET 4.0, NUnit 2.5.5), all seemed to be well at first, and then NUnit could not find any tests. The GUI seems permanently set for .NET 2.0, even when I try to change it. 'nunit-console.exe' works correctly for me when I use the /framework flag, though it did *not* work without the flag, even on a 32-bit machine.

After reading through this bug (after trying various times to run my tests), I checked my Task Manager, and found two entries each of 'nunit-agent.exe' and nunit-agent-x86.exe' (I had closed NUnit itself earlier). Once I killed all four of those processes, the NUnit GUI found my tests again.

I hope this is some help to you -- you've made a great tool that I depend on implicitly.

Thanks,
--Chris Shaw