nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

I see that NUnit.exe is holding handles to the original copy of the
Dlls rather than to
those in the shadow copy cache. Can you think of anything you've done
in your test
setup to defeat the use of the cache?

I've tagged this with 'confirm' to see if somebody else can replicate
it, which may
be helpful. Unfortunately, my own Windows box is being repaired and this is too
much of a system-related bug for me to work it under Linux.

Charlie

On Wed, Sep 15, 2010 at 8:18 AM, Greg Brant <619679@xxxxxxxxxxxxxxxxxx> wrote:
> The attached png has Process Explorer showing that NUnit.exe has handles
> on the DLLs in question.
>
> What other information do you need in order to diagnose this issue?
>
> -----Original Message-----
> From: bounces@xxxxxxxxxxxxx [mailto:bounces@xxxxxxxxxxxxx] On Behalf Of Charlie Poole
> Sent: 14 September 2010 19:51
> To: Greg Brant
> Subject: [Bug 619679] Re: NUnit 2.5.7.10213 GUI TestRunner Locks Test Assembly
>
> ** Tags added: confirm
>
> --
> NUnit 2.5.7.10213 GUI TestRunner Locks Test Assembly
> https://bugs.launchpad.net/bugs/619679
> You received this bug notification because you are a direct subscriber of the bug.
>
> Status in NUnit V2 Test Framework: New
>
> Bug description:
> After opening and running an NUnit project in the GUI test runner I am unable to build my solution in Visual Studio. The build fails with the following error.
>
> Unable to copy file "C:\Projects\Foo\Foo.Bar\bin\Debug\Foo.Bar.dll" to
> "bin\Debug\Foo.Bar.dll". The process cannot access the file
> 'bin\Debug\Foo.Bar.dll' because it is being used by another process.
>
> Foo.Bar.dll is the assembly under test, my tests are in a separate
> assembly, Foo.Bar.Tests.dll which has a referrence to the Foo.Bar
> project.
>
> I have to close the NUnut project, rebuild then reopen the project.
> This was not an issue in NUnit 2.5.3 (2.5.3.9345). The GUI would not lock an files, rebuilding the solution triggered a reload of the assemblies.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/nunitv2/+bug/619679/+subscribe
>
> ----------------------------------
> Inbound email scanned by Mimecast.
> ----------------------------------
>
> -----------------------------------------------------------------------------------------------------------------------------------------
> This email message has been delivered safely by Mimecast.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> ** Attachment added: "file handles.PNG"
>   https://bugs.launchpad.net/bugs/619679/+attachment/1588880/+files/file%20handles.PNG
>
> --
> NUnit 2.5.7.10213 GUI TestRunner Locks Test Assembly
> https://bugs.launchpad.net/bugs/619679
> You received this bug notification because you are a member of NUnit
> Developers, which is subscribed to NUnit V2.
>

-- 
NUnit 2.5.7.10213 GUI TestRunner Locks Test Assembly
https://bugs.launchpad.net/bugs/619679
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:
After opening and running an NUnit project in the GUI test runner I am unable to build my solution in Visual Studio. The build fails with the following error.

Unable to copy file "C:\Projects\Foo\Foo.Bar\bin\Debug\Foo.Bar.dll" to "bin\Debug\Foo.Bar.dll". The process cannot access the file 'bin\Debug\Foo.Bar.dll' because it is being used by another process.

Foo.Bar.dll is the assembly under test, my tests are in a separate assembly, Foo.Bar.Tests.dll which has a referrence to the Foo.Bar project.

I have to close the NUnut project, rebuild then reopen the project. 
This was not an issue in NUnit 2.5.3 (2.5.3.9345). The GUI would not lock an files, rebuilding the solution triggered a reload of the assemblies.