nunit-core team mailing list archive

[Mikael Gustafsson <619679@xxxxxxxxxxxxxxxxxx>]

I tried NUnit the first time today. It seems like great software, unfortunately I have the same problem.
If I close the project in the NUnit GUI the file lock disappears.

"Enable shadow copy" is checked and the "Cache path" is pointing to a valid directory.
The volyme shadow copy service is running.
UAC (user  account control) is turned off, all applications runs as admin.

I use
NUnit 2.5.9
Visual Studio 2008
Vista x64
.NET 2.0 in my project

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/619679

Title:
  NUnit 2.5.7.10213 GUI TestRunner Locks Test Assembly

Status in NUnit V2 Test Framework:
  Fix Released

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.