如何动态链接到尚不存在的目录？
我有一个 InstallScript 项目，我正在考虑将其手动重新创建为基本 MSI 项目。对于InstallScript 项目，我们有几个利用动态文件链接的组件，并链接到路径变量中指定的位置。
但是，当我尝试在 Basic MSI 项目中执行此操作时，我收到一条错误：“您输入的文件夹名称不是系统上的有效文件夹名称。”这是完全正确的 - 指定的目录不存在，但它们将在编译安装程序之前的构建时创建。 InstallScript 项目似乎对动态链接到当前不存在的目录没有任何疑虑。 Basic MSI 拒绝这样做。
有什么方法可以链接到尚不存在的目录吗？我是否需要在这些位置创建虚拟文件夹来安抚 InstallShield？
I have an InstallScript project that I'm looking at manually recreating as a Basic MSI project. For the InstallScript project, we have several components that utilize dynamic file linking, and link to a location specified in a path variable.
However, when I attempt to do this in the Basic MSI project, I receive an error: "The folder name you have entered is not a valid folder name on your system." This is completely correct - the specified directories don't exist, but they will be created at build time, before the installer is compiled. The InstallScript project seemed to have no qualms about dynamically linking to a directory that does not currently exist. The Basic MSI refuses to do it.
Is there any way to link to directories that don't exist (yet)? Do I need to create dummy folders in these locations to appease InstallShield?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我根本不支持动态链接，但如果必须的话，只需创建一个空目录，构建自动化将在其中创建它，然后设置动态链接。 （按合同设计。）
当然，这就是动态文件链接的问题......与实际描述哪些文件安装在哪里相比，没有太多合同。 YMMV。
Not the I endorse dynamic linking at all, but if you must, just create the empty directory where the build automation will create it and then setup your dynamic links. ( Design by contract. )
Course that's the problem with dynamic file linking...... there isn't much of a contract as compared to actually describing which files get installed where. YMMV.