Simone, If you refer to the bug description, you may find that I used Process Explorer to ensure that a handle to the assembly was actually held by the NUnit GUI process.
Regards, Vitalii -- 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 _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : nunit-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
