nunit-core team mailing list archive

[Martin Jones <582051@xxxxxxxxxxxxxxxxxx>]

Charlie,

I have failed to reproduce the original error on my 64 bit machine, and 
it didn't happen on the 32 bit machine at all. That of course doesn't 
mean that the 32 bit machine doesn't suffer the problem, just that I 
haven't seen it.

One thing to consider with the information in this post is that the 
original fault occured on 64 bit vista. I am now on 64 bit Win 7, and no 
longer have the old machine available.

I found that I had to restart the 64 bit machine before I could edit the 
app config file. Something had it locked, but all applications had been 
closed and there was no agent running in the task manager. I was going 
to get the sysinternals tools to find out which process, but once again, 
the problem has snuck away. So, I haven't been able to determine which 
process had it locked. I don't know if this will ever be relevant though.

I needed to edit the config file to put it back into the non-workaround 
situation. However, after doing this, nunit worked fine and showed the 
v2 stuff in the gui, and the v4 stuff in the agent.

I have played around with my firewall settings to see if that could 
possibly affect it. I was trying to think of something that would happen 
first time you ran it, and then didn't affect it later. However, getting 
the firewall to block both processes, or prompt for what to do for both 
processes didn't generate the error.

So, sorry, but I can't answer the question :-(

On the 2.5.5 and v4 bit: I probably misinterpreted Jv's comment on NUnit 
2.x.x. not recognizing .net 4. Yes, it does work on my machines.

Thanks,

Martin

Charlie Poole wrote:
> I just re-read the thread, including some items I missed...
> 
> It is NOT correct that NUnit 2.5.5 is "not supposed to work" with .NET 4.0. Indeed,
> it does work , at least - as the saying goes - on my machine.
> 
> Workarounds are well and good, but it would be great to continue to try to identify
> what isn't working as it should and fix it!
> 
> Here's a question for all who reported the bug. Is this only present on 64-bit
> machines? If you have a bug running on a 32-bit OS, is it the same stack trace?
> 
> Charlie
>

-- 
2.5.5 cannot find fixture for framework 4.0
https://bugs.launchpad.net/bugs/582051
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:
Just downloaded v2.5.5.10112 of Nunit. In a new VS2010 project I am unable to get either the nunit.exe or nunit-console.exe programs to recognize my test cases. The programs run, and after a while tell me 'can't find test fixture' in the case of nunit-console, and a similar message with nunit. The test class has TestFixture applied, and is public, the method has TestCase applied (started as Test) and is also public. The project has references to the 2.5.5 versions of nunit.core.dll and nunit.framework.dll.

I changed the target runtime to 3.5, recompiled, and it has picked up on the test cases immediately (I'm still using the 2.5.5 dlls).

Possibly of interest, the gui really wants to use version 2 of the framework. I tried requesting version 4 from the menu but after a while, it fails to find the test and reverts back to version 2 of the framework.

I'm using VS2010 (evaluation edition at the moment), on 64 bit Vista.

I've tried to find a solution elsewhere, and full apologies in advance if it's a school-boy error on my part.

Thanks for your time on the project.