Hi Jv, Thanks for the quick response, and can I just quickly say thankyou, thankyou very much for nunit. I'm having trouble repeating the bug this morning, I remember that there was something I left off the report last night that might be useful. Let me explain what I have done first though. The VS solution is in SVN so I checked it out to a 32 bit machine, and left it in it's current 'target framework 3.5' position and it worked fine. I changed the solution to target to framework 3.5 and it worked fine as well. All of the target changes are on the VS projects, not nunit. I went back to the 64 bit machine, reloaded the project and checked that it still worked with a framework 3.5 target. It did. I then changed it to a 4.0 project and it worked! I do not believe that anything else had changed. In case there was something being affected by it having run once, I created a new 64 bit, very simple test project, and it ran fine. In all these cases I am running a class library by setting the debug executable to nunit.exe and giving it the name of the .dll containing the testing code - I don't use an .nunit file. So, I have been unable to repeat the issue I was having last night. I'm sure you get some bogus bug reports, and I'll be the first one to admit that I can make silly mistakes, but I really haven't made any changes from last night other than moving it back to a framework 4.0 target. Last night, there was one odd thing that happened while initially trying to get nunit running. I had the error about not finding the test fixture on the very first run. On the second attempt, I believe it found the text fixture, but not on any subsequent runs. I believe that it was the nunit 2.5.5 version that was running because visually it appeared slightly different (with the tick marks) to 2.4.8 that I had been using previously. The reason that I didn't include it in the report last night was that I was working with two solutions and assumed that I had accidently run an old solution where I was copying the using statements from. Because I couldn't repeat it - I put it down to this other solution and assumed that I was mistaken. I'm not so sure now. My solution is now set to framework 4.0 and I will be using nunit 2.5.5.10112 for the next couple of days. If I can reproduce the error once more, then I will let you know. If I do reproduce the error, should I reply to this email again? Martin Jv wrote: > Hi Martin, > > I installed VS 2010 Ultimate in my machine to replicate your bug scenario > but it works in my machine properly. I saved the .nunit project file in the > bin\debug folder of my VS 2010 test project using Nunit 2.5.10112. I ran the > tests using the default project settings, which says use the default version > of the framework (which will translate to whichever framework against which > the test assembly has been compiled with) and it works absolutely fine. > > So, the only difference seems to be in your 64 bit machine. I will try to > replicate the scenario in a 64-bit machine and let you know. kindly reply if > the assembly gets loaded on a 32 bit machine then we will be sure that it is > something specific to 64-bit machines. > > Regards, > > Jv > http://ravichandranjv.blogspot.com > On Tue, May 18, 2010 at 9:20 AM, Martin Jones