nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Hi Marc,

Yeah... the "other process" was actually the same process. It's a common error
message failure to communicate.

@Greg: is this any help to you?

Charlie

On Thu, Sep 16, 2010 at 6:14 PM, Marc Durham <619679@xxxxxxxxxxxxxxxxxx> wrote:
> OK now I think I've got it:
> In the NUnit GUI I clicked "Project", "Edit..."
> Then I noticed that the "Project Base:" path was not the base folder for my project, it was a subfolder that I had made for the NUnit project file.
>
> So I changed the "Project Base:" to the correct folder (all I did was
> delete the last part of the path, the subfolder) and now it works, I can
> build my assembly while the NUnit GUI is running without having to close
> it and open it again every time I want to build or test.  I don't get
> the "opened by another process" error message when I click "Build."
>
> --
> 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.