Windows应用程序安装程序框架 [英] Windows application installer frameworks

问题描述

对我来说，可下载的应用程序会提供多种类型的安装程序总是让我感到奇怪.例如，有时您可以选择.exe或.msi

It's always seemed strange to me that downloadable applications would offer multiple types of installers. For example, sometimes you can choose either a .exe or a .msi

某些类型的安装程序是否比其他类型的安装程序具有优势?选择哪一个有关系吗?作为开发人员，我为什么要为用户提供不同的安装程序?

Do certain types of installers have advantages over others? Does it matter which one you choose? As a developer, why would I want to offer different installers to my users?

推荐答案

exe和msi之间的一个大区别: 您可以编辑一个MSI文件.
您可以直接使用 Orca 访问MSI数据库-使用您最喜欢的Windows黑客方法，通过WindowsInstaller API对其进行编码.

One big difference between the exe and msi: You can EDIT an MSI file.
You can access the MSI Database directly using Orca -or- code it up through the WindowsInstaller APIs, using your favorite Windows hacking methods.

例如我写了一个基于python的构建器，它除了执行许多其他任务外，还定期编辑和更新MSI软件包.

Ex. I wrote a python based builder which, amongst many other tasks, routinely edits and updates MSI packages.

勇敢的灵魂的快速警告:

尽管API 似乎有据可查，但许多WI功能却是微妙的，甚至是神秘的-MS Office团队肯定没有 not 选择最不令人惊讶"的原则当他们创建Windows Installer时.

Although the APIs seem well documented, a LOT of WI functionality is subtle, even cryptic - the MS Office team definitely did not chose the principle of "least surprise" when they created Windows Installer.

如果，您选择深入研究WI的神秘世界，为长时间的头部抓挠，繁琐的调试以及倾倒大量的MSI日志文件做好准备

IF you choose to delve into the mystic world of WI, be prepared for long hours of head scratching, tedious debugging and pouring over enormous MSI log files

这篇关于Windows应用程序安装程序框架的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！