安装 ODBC 驱动程序时，Windows Installer 始终将其放入 SystemFolder
我正在开发一个安装程序，除其他外，它还可以安装网络服务器。 作为设置的一部分，我将设置 ODBC 驱动程序和数据源。我是 试图放入一堆实用程序文件，包括第三方 ODBC 驱动程序 DLL， 进入某个文件夹，但是当我运行安装程序时，它坚持要更改 将该目录复制到 SystemFolder 目录。为什么要这样做，并且是 有什么方法可以让它把文件安装到我想要的地方吗？ 奇怪的是，它实际上工作正常，直到我添加了一堆 更多文件到该特定文件夹。如果相关的话，我遇到问题的文件位于合并模块中。
（我暂时解决了这引起的问题 将 DLL 安装到 SystemFolder，但我宁愿通过以下方式避免 DLL 地狱 将其安装在我想要的位置，而不是 Windows Installer 看起来的位置 我认为它应该消失。）
我还应该指出，我正在使用 Wise Installation Studio 7.0 作为我的开发环境。
I'm working on an installer that, among other things, installs a web server.
As part of the setup, I'm setting up an ODBC driver and data source. I'm
trying to put a bunch of utility files, including the third party ODBC driver DLL,
into a certain folder, but when I run the installer, it insists on changing
that directory to the SystemFolder directory. Why is it doing this, and is
there any way that I can make it install the files where I want them to go?
Strangely enough, it was actually working correctly up until I added a bunch
more files to that particular folder. In case it's relevant, the files that I'm having trouble with are in a merge module.
(I'm temporarily getting around the problems that this is causing by
installing the DLL to the SystemFolder, but I'd much rather avoid DLL hell by
having it installed where I want it to go, not where Windows Installer seems
to think it should go.)
I should also point out that I'm using Wise Installation Studio 7.0 as my development environment.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
似乎不是 Windows Installer 坚持将 ODBC 驱动程序 DLL 安装在 SystemFolder 目录中，而是 Wise。我们发现这个解决方案用于消除我们也看到的错误 1918 问题，该问题表示将驱动程序条目从 ODBCDriver 表中取出，并将它们作为注册表条目粘贴进去。实施该修复后，我们尝试将 DLL 移动到我们真正想要安装它的位置，安装程序对此感到满意。
It would seem that it's not Windows Installer that insists on the ODBC Driver DLL being installed in the SystemFolder directory, but Wise. We found this solution for getting rid of an Error 1918 problem that we were also seeing, which says to take the driver entries out of the ODBCDriver table, and stick them in as Registry entries instead. After implementing that fix, we tried moving our DLL to where we really want it to be installed, and the installer was happy with that.