nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Hi Greg,

If you change the Process Model setting to "Run tests directly in the
NUnit process"
do you still have the same problem?

Charlie

On Fri, Aug 20, 2010 at 12:45 AM, Greg Brant <619679@xxxxxxxxxxxxxxxxxx> wrote:
> Hi Charlie,
>
>
> Here’s my Test Assemblies
>
>
> ==========================================================================================
>
> nunit.exe ( 5812 )
>
>  CLR Version: 2.0.50727.4952 ( Net 2.0 )
>
>
> nunit-agent.exe ( 4752 )
>
>  CLR Version: 2.0.50727.4952 ( Net 2.0 )
>
>
>  test-domain-ProjectName.nunit
>
>    ApplicationBase: C:\Projects\web\ProjectName\Solution Items
>
>    PrivateBinPath: ..\ProjectName.Commerce.Tests\bin\Debug
>
>                    ..\ProjectName.Core.Tests\bin\Debug
>
>    Configuration File: C:\Projects\web\ProjectName\Solution
> Items\ProjectName.config
>
>    ProjectName.Commerce.Tests
>
>      Path:
> C:/Projects/web/ProjectName/ProjectName.Commerce.Tests/bin/Debug/ProjectName.Commerce.Tests.dll
>
>      Image Runtime Version: 2.0.50727
>
>      Uses: nunit.framework, Version=2.5.7.10213, Culture=neutral,
> PublicKeyToken=96d09a1eb7f44a77
>
>    ProjectName.Core.Tests
>
>      Path:
> C:/Projects/web/ProjectName/ProjectName.Core.Tests/bin/Debug/ProjectName.Core.Tests.dll
>
>      Image Runtime Version: 2.0.50727
>
>      Uses: nunit.framework, Version=2.5.7.10213, Culture=neutral,
> PublicKeyToken=96d09a1eb7f44a77
>
> ==========================================================================================
>
>
> The DLL is built to .net 3.5. I'm running Windows 7 pro 64bit.
>
>
> In settings, under Test Loader / Assembly Isolation I've got "Run tests
> in a single separate process" checked.
>
>
>
>
> Cheers,
>
> Greg
>
>
>
>
> -----Original Message-----
>
> From: bounces@xxxxxxxxxxxxx [mailto:bounces@xxxxxxxxxxxxx] On Behalf Of
> Charlie Poole
>
> Sent: 18 August 2010 14:22
>
> To: Greg Brant
>
> Subject: Re: [Bug 619679] [NEW] NUnit 2.5.7.10213 GUI TestRunner Locks
> TestAssembly
>
>
> Your tests may be loaded in different ways under 2.5.7, so we'll need
> more info.
>
>
> Take a look at Tools | Test Assemblies in the Gui - what version of .NET
> is being used for NUnit itself and what version for the tests? Are the
> tests running directly under nunit.exe or under nunit-agent.exe?
>
>
> Charlie
>
>
> On Wed, Aug 18, 2010 at 1:01 AM, Greg Brant <619679@xxxxxxxxxxxxxxxxxx>
> wrote:
>
>> Public bug reported:
>
>>
>
>> 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 reference 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.
>
>>
>
>> ** Affects: nunitv2
>
>>     Importance: Undecided
>
>>         Status: New
>
>>
>
>> --
>
>> 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 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 reference 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: "unnamed"
>   https://bugs.launchpad.net/bugs/619679/+attachment/1502892/+files/unnamed
>
> --
> 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.