链接 MSI 安装程序工具
我正在寻找一个支持连锁 MSI 安装的工具（最好不是 InstallShield，而且最好是便宜/免费）。我有几个小型安装需要能够单独部署，但也需要作为一个组进行部署，并且我不想维护多个安装程序。
看起来我需要 Windows Installer 4.5 才能正确执行此操作，但当我查找支持的安装程序版本时，我似乎找不到太多信息。
I'm looking for a tool (preferably not InstallShield, and also preferably cheap/Free) that supports Chained MSI Installations. I've got several small installations that need to be able to be deployed separately, but also as one group, and I'd like to not have to maintain multiple installers.
It looks like I need Windows Installer 4.5 to do this properly, but I can't seem to find to much info when I'm looking around for what version of Installer is supported.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
MSI 4.5 功能只是一组 API，允许引导程序/链接程序为多个 MSI 执行更智能的操作。您仍然需要引导程序/链接器来安装多个软件包。在 WiX v3.6 将刻录。
The MSI 4.5 functionality is just a set of APIs that allow bootstrapper/chainers to do smarter things for multiple MSIs. You still need a bootstrapper/chainer to install multiple packages. In WiX v3.6 there will Burn.
顺便说一句，虽然不是特别容易，但它曾经可以“嵌套”或将其他 MSI 嵌入到一个父级中，但它涉及调整自定义操作等，以确保在删除父级等时删除嵌套程序遗憾的是，此功能已“弃用” 因此 Microsoft 不再推荐。这是如何在 Visual Studio 安装程序项目中执行此操作...但是创建更建议使用 WiX 的引导程序。
Incidentally, it used to be possible--although not particularly easy--to "nest" or embed other MSIs into one parent, but it involved tweaking custom actions and such to ensure that the nested programs were removed upon removal of the parent, etc. Sadly, this feature is "deprecated" and thus no longer recommended by Microsoft. Here's how to do it in a Visual Studio installer project... but creating a bootstrapper with WiX would be more advised.
你需要的是一个引导程序。使用 InstallShield 或 Wix 会自行创建一个 MSI，当该 MSI 运行时，将不允许其他较小的 MSI 运行。如果您已经有较小的 MSI 来运行引导程序，那么您所需要的就足够了。
MSDN 有一个免费的版本，您可以下载它插入 VS2008 并使用 MSBuild 进行编译。您可能需要做的是为您的 MSI 创建包并将它们作为先决条件放入引导程序中。这将允许您将其设置为按特定顺序运行它们。
以下是 MSDN 链接：MSDN Bootstrapper Manifest Generator
What you need is a bootstrapper. Using and InstallShield or Wix will created an MSI themselves which when that is running will not allow the other smaller MSIs to run. If you already have the smaller MSIs to run a bootstrapper is all you need.
MSDN has a free one you can download that plugs into VS2008 and uses MSBuild to compile. What you will probably need to do is create packages for your MSIs and put them in the bootstrapper as prerequisites. This will allow you to set it up to run them in a particular order.
Here is the MSDN link: MSDN Bootstrapper Manifest Generator
看看 NSIS
Look at NSIS