由于 win 资源管理器指向的目标发布文件夹，是否有针对 ISDEV 致命错误 -1014 的自动解决方案？
我的 installshield 项目构建出现了这样的错误：
“ISDEV：致命错误-1014：无法重命名目录*\发布到 *\Release.Bak。 Windows 资源管理器或 DOS 提示符可能指向发布输出文件夹 (Disk1) 的子文件夹或 Interm 文件夹，锁定它。更改当前目录。关闭所有打开的文件 在 Disk1 文件夹中。如果 Msidb.exe 打开，请将其关闭。”
原因是因为在我开始构建之前，我打开了一个 win 资源管理器，它指向该发布文件夹。不知何故，ISDEV 认为这是锁定该文件夹，因此它拒绝继续 ”
现在，有没有一种方法，例如添加某种脚本，可以在构建脚本开始之前强制关闭所有打开的 win 资源管理器实例以释放所谓的“锁定
？
My installshield project build gave such error:
"ISDEV : fatal error -1014: Cannot rename directory *\Release to
*\Release.Bak. Windows Explorer or a DOS prompt may be pointing to a subfolder of the release output folder (Disk1) or to the Interm
folder, locking it. Change the current directory. Close any open files
in the Disk1 folder. Close Msidb.exe if it is open."
The reason is because before I started the build I got a win explorer opened which was pointed to that release folder. And somehow ISDEV consider this as locking the folder, so it refused to proceed with the renaming.
Now, is there a way, like add some sort of script, to forcefully close all opened win explorer instance to release the socalled "lock" before the build script starts?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
我知道这是一个旧线程，但问题仍然存在。
该错误似乎与锁定文件夹的另一个进程无关。我认为 InstallShield 试图重命名 IT 仍打开一些文件的文件夹，这是在与自己作斗争。这就是为什么许多传统方法（例如关闭资源管理器甚至重新启动）有时不起作用的原因。
我发现一个相当简单的解决方案是在进行构建之前从安装项目文件夹中删除文件夹树 \Express。 InstallShield 只是重新创建它，一切正常，因为不需要重命名。
I know this is an old thread, but the problem is still around.
It seems the error is nothing to do with another process having the folder locked. I think InstallShield is fighting with itself by trying to rename a folder where IT still has some files open. That's why many of the traditional approaches such as closing explorer and even rebooting sometimes don't work.
I found a fairly simple solution is to delete the folder tree \Express from the Setup project folder before doing a build. InstallShield just recreates it and everything is OK because the rename was not needed.
自从我记得在我的第一个 IntallShield 中工作以来，这个问题就一直存在。
不要试图打破锁定。只需确保在构建之前不要在发布文件夹上保持资源管理器打开。但是，您可以导航到其父文件夹或更好：定义 构建后分发事件。
This issue has been around as long as I remember working in my first IntallShield.
Don't try to beat the locking. Just make sure you don't keep explorer open on the release folder prior to the build. You can however navigate to its parent folder or better yet: define a post build distribution event.
我发现删除该文件夹的方法是在预构建事件中放置类似的内容：
因为 InstallShield 项目没有与其他项目相同的属性，所以我已将其插入到预构建事件的属性中解决方案的主要项目。
The way I have found to remove that folder is to put something like this in the pre-build events:
Because InstallShield project does not have the same properties as other projects do, I have inserted that in the Pre-build events at the properties of the main project of the solution.
遇到了同样的问题，只需关闭 InstallShield 并重新打开它，就可以了。
Had the same problem, just closed InstallShield and re-opened it, worked like a charm.
遇到了同样的问题，通过结束此任务“InstallShield (R) 64-bit Setup Engine”来修复它
Had the same problem, fixed it by Ending this task "InstallShield (R) 64-bit Setup Engine"