为什么在Resharper / MSTest下调试时引用的DLL被锁定？ [英] Why is referenced dll getting locked while debugging under Resharper/MSTest?

问题描述

我有一个汇编程序的集成测试 A 。通过项目参考汇编 A 引用程序集 B 。我在Resharper 6.1单元测试场景下，在Visual Studio 2010调试器下运行它们。测试引擎是Microsoft的本地MSTest。

I have an integration test for a method in assembly A. Assembly A references assembly B via project reference. I run them under the Visual Studio 2010 debugger in a Resharper 6.1 unit testing scenario. The testing engine is Microsoft's native MSTest.

我得到臭名昭着的

进程无法访问文件 ... \B.dll ，因为它被另一个进程使用。

The process cannot access the file ...\B.dll because it is being used by another process.

消息。我已经验证没有其他进程对该文件具有处理（例如通过Sysinternal的Process Explorer）。

message. I have verified that no other process has a handle on that file (e.g. via Sysinternal's Process Explorer).

从调试器运行测试工作正常。任何想法，为什么它会发生在调试器下，我可以做什么来解决它？

Running the test out of the debugger works fine. Any ideas why it happens under the debugger and what I can do to fix it?

推荐答案

我看到类似的情况，在任务管理器中找到vtest.discoveryengine.exe和vtest.executionengine.exe仍然存在。我杀了两个，解决了这个问题。

I have seen a similar situation, and found in the task manager that vtest.discoveryengine.exe and vtest.executionengine.exe were still alive. I killed both, which solved the problem.

这篇关于为什么在Resharper / MSTest下调试时引用的DLL被锁定？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！