Visual Studio 11 开发预览：无法删除thumbs.db
我在 Windows 8 开发人员预览版下的 Visual Studio 11 开发人员预览版中的开发工作流程遇到了严重问题。这是我所看到的，其他朋友也看到了同样的情况。
- 打开 Visual Studio
- 创建新的空白 Javascript 应用程序
- 添加非常基本的代码以添加标签（代码和项目似乎并不重要）
- 开始调试（本地计算机）
- 工作正常
- 停止调试
- 再次运行
- 构建完成
部署步骤失败< /p>
1>------ 构建开始：项目：MyProject，配置：调试任何 CPU ------ 1>我的项目-> C:\Users\mmoser\Documents\Visual Studio 11 \Projects\MyProject\MyProject\Debug\MyProject.build.appxrecipe 2>------ 部署开始：项目：MyProject，配置：调试任何 CPU ------ 2>错误DEP0500：无法删除文件夹“C:\Users\mmoser\AppxLayouts\MyProject.Debug.AnyCPU.mmoser”，原因如下： 2>该进程无法访问文件“Thumbs.db”，因为该文件正在被另一个进程使用。 2>发生一个或多个错误。 ========== 构建：1 成功，0 失败，0 最新，0 跳过 ========== ========== 部署：0 成功，1 失败，0 跳过 ==========
尝试从 Windows 资源管理器中删除文件夹，同样的错误
- 等待几秒钟到一分钟左右
- 再试一次，它可以工作
这是非常具有破坏性的，我无法继续开发我的应用程序。我正在和一个朋友一起开发这个，他现在也遇到了同样的问题。
我们想知道 Visual Studio 是否未正确释放对部署文件夹的访问权限？
对此的任何帮助都会很棒！我发现自己陷入困境，我们的项目陷入停滞......请帮忙！
I'm running into a serious issue with my development workflow in Visual Studio 11 Developer Preview under Windows 8 Developer Preview. Here's what I am seeing and other friends are seeing the same.
- Open Visual Studio
- Create New Blank Javascript Application
- Add very basic code to add a label (code and project doesn't seem to matter)
- Start With Debugging (Local Machine)
- Work Fine
- Stop Debugging
- Run Again
- Build Completes
Fails on Deploy Step
1>------ Build started: Project: MyProject, Configuration: Debug Any CPU ------
1> MyProject-> C:\Users\mmoser\Documents\Visual Studio 11 \Projects\MyProject\MyProject\Debug\MyProject.build.appxrecipe
2>------ Deploy started: Project: MyProject, Configuration: Debug Any CPU ------
2>Error DEP0500 : Cannot delete the folder "C:\Users\mmoser\AppxLayouts\MyProject.Debug.AnyCPU.mmoser" for the following reason:
2>The process cannot access the file 'Thumbs.db' because it is being used by another process.
2>One or more errors occurred.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========Try to delete folder from Windows Explorer, same error
- Wait an anywhere from a few seconds to a minute-ish
- Try again and it works
This is very disruptive and I'm unable to continue development on my application. I am developing this with a friend and he is now seeing the same problem.
We are wondering if Visual Studio is not properly releasing access to the deployment folders?
Any help with this would be amazing! I am finding myself stuck and our project stalled...please help!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
thumbs.db 文件是由 Explorer 创建的文件，包含缩略图预览图像。
您是否偶然在 AppX 布局文件夹中打开了一个资源管理器窗口？本例中的布局文件夹为“C:\Users\mmoser\AppxLayouts\MyProject.Debug.AnyCPU.mmoser”。锁定的文件会阻止我们更新布局文件夹，因此部署将会失败。
仅供参考：我在 MS 的 VS Pro 团队工作。如果您仍然遇到问题，请提交 Connect bug，我们可以查看。 (http://connect.microsoft.com/)
The thumbs.db file is a file created by Explorer and contains the thumbnail preview images.
Do you by chance have an Explorer window open in the AppX layout folder? The layout folder in this case is "C:\Users\mmoser\AppxLayouts\MyProject.Debug.AnyCPU.mmoser". Locked files prevent us from updating the layout folder, and hence deployment will fail.
FYI: I work for MS on the VS Pro team. If you continue to have an issue, please file a Connect bug, and we can take a look. (http://connect.microsoft.com/)
总之，我与 BUILD 的 VS 团队进行了交谈并解决了该问题。谢谢基兰·莫克福德！看起来有几种情况，进程没有完全关闭，它们可以在开发工作流程中保留布局文件和可能的其他文件。
我现在知道的三种情况是：
WWAHost.exe 仍在运行（Javascript 应用程序），并且
有权访问这些文件。
导致其他文件访问问题（不是我在本文中描述的一次）
帖子）
而且这并不总是被关闭。
如果您在尝试构建或部署时遇到锁定文件问题，我建议您从 sysinternals 下载 Process Explorer 并查看哪些进程正在保存您的文件。然后在任务管理器中将其杀死。
注意：我的问题是#1。我正在构建一个 JavaScript 应用程序，WWAHost（Windows Web 应用程序主机）进程仍在运行。
All, I spoke with the VS team at BUILD and resolved the issue. Thanks Kieran Mockford! It looks like there are several senarios where processes are not fully shut down and they can hold on to the layout files and potentially other files during the development workflow.
The three senarios I know of now are:
the WWAHost.exe is still runing (Javascript applications) and this
has acess to the files.
cause other file access issues (not the onces I described in this
post)
and this does not always get shut down.
If you are running into locked file issues what trying to build or deploy, I would recommend downloading Process Explorer from sysinternals and seeing what process is holding onto your files. Then kill it in Task Manager.
Note: My issue was #1. I was building a JavaScript application and the WWAHost (Windows Web Application Host) process was still running.