NUnit:“该进程无法访问该文件......因为它正被另一个进程使用."

本文介绍了NUnit:“该进程无法访问该文件......因为它正被另一个进程使用."的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我使用的是 NUnit GUI 版本，当我在其中加载了一个测试项目来尝试测试时，它开始对我感到不安.如果我在 Visual Studio 中进行更改，然后尝试重建解决方案，则会引发错误无法将文件 obj\Debug\foo.dll 复制到 bin\Debug\foo.dll.进程无法访问文件 bin\Debug\foo.dll 因为它正被另一个进程使用."

I'm using the NUnit GUI version, and it started to get upset at me when I have a test project loaded in there trying to test things. If I make a change in Visual Studio, and then try to rebuild the solution, it throws the error "Unable to copy file obj\Debug\foo.dll to bin\Debug\foo.dll. The process cannot access the file bin\Debug\foo.dll because it is being used by another process."

当然，这是我加载到 GUI 中的 DLL.以前还可以，只是在构建后刷新项目引用，但现在它似乎阻止了它.我怎样才能恢复这种行为?

This is the DLL I have loaded into the GUI, of course. It used to be OK, and just refresh the project reference after a build, but now it seems to be blocking it. How can I get back to that behavior?

顺便说一下，我试过启用/禁用卷影复制设置，结果都一样.

I've tried enabling/disabling the shadow copy setting by the way, with the same results either way.

VS2008 SP1 和 NUnit 2.4.8，如果这很重要.

VS2008 SP1 and NUnit 2.4.8, if that matters.

推荐答案

想通了:卷影复制"服务因某种原因被关闭.重新开机，一切恢复正常.

Figured it out: the "Volume Shadow Copy" service was shut off for some reason. Turned it back on, and everything's back to normal.