nunit-core team mailing list archive

[Simone Busoli <985861@xxxxxxxxxxxxxxxxxx>]

Hi Vitalii, the fact that Visual Studio reports the dll as being locked
doesn't necessarily mean that the NUnit Gui is locking it.

May I ask what leads to you believe that NUnit itself is locking the
assembly?

Also, if you can create a repro which doesn't use your production code
we may be able to try it ourselves.

-- 
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:
  Incomplete

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