nunit-core team mailing list archive

[Vitalii Maklai <vmcl@xxxxxxxxxx>]

Charlie,

Currently, I've got only one test assembly containing a few fixtures and
experiencing the problem mentioned above.

I verified the references. Among NUnit dlls, only nunit.framework  is referenced. Also, there is a reference to Moq.dll.
All other references are production projects or .NET Framework assemblies. 

FYI, I'm using the assembly reload settings as at the screenshot
attached.

** Attachment added: "AsmReloadSettings.jpg"
   https://bugs.launchpad.net/nunitv2/+bug/985861/+attachment/3096297/+files/AsmReloadSettings.jpg

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

Title:
  Test assemblies are locked

Status in NUnit V2 Test Framework:
  New

Bug description:
  NUnit GUI 2.6.0.12051
  FW 4.0

  After a test run, the test assemblies are locked by NUnit process
  though "Enable Shadow Copy" option is on.

  I was experiencing this issue in both of the following cases:
    (a) FW runtime 4.0 is forced in NUnit config file and test assemblies are for FW 4.0
    (b) default runtime settings are used and test assemblies are for FW 4.0

  I ran Sysinternals' ProcessExplorer and ensured that NUnit process was
  holding a handle to the referenced test assembly (not a shadow copy
  instance).

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/985861/+subscriptions