工具:有许多工具可用于 MSI 创建.一些商业和 WiX - 开源解决方案.这里是工具的快速摘要.商业工具非常好但价格昂贵，WiX(免费，开源)也非常好，但有一个学习曲线(XML 文本源).请记住，在大多数情况下，设置顾问可以帮助您快速制作此类​​软件包，但您可能需要内部知识.工具长篇回顾.

Tools: There are a number of tools available for MSI creation. Some commercial and WiX - the open source solution. Here is a quick summary of tools. The commercial tools are excellent but expensive, WiX (free, open source) is also excellent but has a learning curve (XML text sources). Remember that a setup consultant can help you make such packages pretty quickly in most cases, but you might need the knowledge in-house. Long review of tools.

凝聚力&耦合:您可能需要创建 3 个不同的 MSI 来安装这些产品，或者您可以将它们全部放在同一个 MSI 中.这里有一些注意事项来决定做什么.记住不要教条但要实用——什么最适合您的特定情况?您可以通过公开您制作的 MSI 中的功能来仅允许安装某些工具 - 仅允许从单个 MSI 安装某些功能.功能示例截图.

Cohesion & Coupling: You might need to create 3 different MSIs to install these products, or you could put them all in the same MSI. Here are some considerations to decide what to do. Remember to not be dogmatic but practical - what will work best for your particular case? You can allow only some of the tools to be installed by exposing features in the MSI you make - allowing only some features to be installed from a single MSI. Feature sample screenshot.

Setup.exe:还有一个功能允许 setup.exe 引导程序/安装程序启动程序按顺序安装包装在其中的多个 MSI 文件.WiX 有刻录组件，商业工具有相同的各种选项(InstallShield Suite 项目，先决条件等... - 此处的信息).

Setup.exe: There is also functionality to allow a setup.exe bootstrapper / installer launcher to install multiple MSI files wrapped inside it in sequence. WiX has the Burn component, and commercial tools have various options for the same (InstallShield Suite Projects, prerequisites, etc... - info here).

详细信息:关于实际设置.您需要确定他们实际安装了什么(子弹第 3) 点 - 先决条件和所有条件(COM、COM+、GAC、Java、VC++ 运行时等...).通过1) 内部专业知识(开发人员)文档，您可能会或可能不会获得这些信息.2) 可以解压文件从setup来看(检查是否是setup.exe中已经出来的MSI文件！)，3) 使用依赖/分析工具安装设置并检查应用程序操作.4) ***是找到旧的安装脚本用于编译旧的安装程序.5) 您还可以捕获"旧的安装 EXE 文件自动转换为 MSI.这有时需要专家进行认真的清理，并且通常需要昂贵的工具.在此处查看更多信息.可能还有进一步的方法.开发人员将转储文件到位，开始注册它们并安装运行时并继续进行直到事情(似乎)可以工作，以便弄清楚在设置中要做什么(让他们记下一些好的笔记).

Details: As to the actual setups. You need to determine what they actually install (bullet point 3) - prerequisites and all (COM, COM+, GAC, Java, VC++ runtime, etc...). That might or might not be available to you via 1) documentation of in-house expertise (developers). 2) You can extract files from the setup to look at (check if they are MSI files already coming out of the setup.exe!), 3) install the setups and inspect the application operation with dependency / profiling tools. 4) The best is to find the old setup scripts used to compile the old setup exes. 5) You can also "capture" old setup EXE files to auto-convert to MSI. This needs serious cleanup at times from experts and it requires expensive tools - generally. See more info here. There are probably further approaches too. Developers will dump files in place, start registering them and install runtimes and keep going until things (appear) to work in order to figure out what to do in the setup (have them jot down some good notes).

打包团队:请注意，大多数大公司都有完整的团队来处理此类设置到 MSI 的转换 - 通常称为应用程序打包".如果您在一家大公司，也许可以尝试找到他们并看看他们是否可以提供帮助(或者只是让他们为您捕获您的设置 - 使用昂贵的工具 - 供您清理 - 清理不是野餐).

Packaging Team: Note that most big companies have whole teams to take care of such setup conversion to MSI - generally referred to as "application packaging". If you are in a big company, maybe try to locate them and see if they can help (or just get them to capture your setup for you - with the expensive tool - for you to clean up - it is no picnic to clean).

链接:

• 有关功能、setup.exe 启动器以及如何分解和捆绑设置的详细解答