使用什么安装产品?InstallShield、WiX、Wise、高级安装程序等 [英] What installation product to use? InstallShield, WiX, Wise, Advanced Installer, etc
问题描述
我目前正在对移除我们目前使用的安装包 (Wise Installer 9) 并转向可以处理诸如 Windows Vista、Windows 7 和 64 位系统之类的安装包进行一些调查.安装程序的本地化将大有裨益，因为我们也有许多法裔加拿大客户.
I'm currently doing some investigation on moving off of the installation package we currently use (Wise Installer 9) and moving to something that will handle things like Windows Vista, Windows 7 and 64-bit systems. Localization of the installers would be of benefit since we do have a number of French Canadian clients as well.
我们目前安装了以下技术的软件包和实用程序:
We currently have installations for software packages and utilities in the following technologies:
- 进度 4GL
- Visual Studio 2005
- Visual Studio 2008
- .NET 精简框架 3.5
我已经看过WiX 和InstallShield，以及 Altiris 替换了旧的 Wise 系统.
I've already looked at WiX and InstallShield, and also the Altiris made replacement for the old Wise system.
我还没有怎么玩过 InstallShield，但从我见过/安装的所有东西来看，它似乎是业界的最爱之一.我浏览了一些与 InstallShield 相关的 Stack Overflow 标签，我很想知道该小组对此有何评论.
I haven't played with InstallShield much at all yet, but from everything I've seen/installed it seems to be one of the industry favourites. I've browsed through some of the Stack Overflow tags relating to InstallShield and I'm curious to see what the group says about it.
我是否只是默认去找他们?WiX 在非 .NET 方面的表现如何?
Do I just by default go to them? How good is WiX at non-.NET stuff?
推荐答案
UPDATE，2018 年 8 月，一个新的更短的选项:如何创建 Windows 安装程序.专注于总结
MSI 及其主要优势，并列出可用的主要工具(附有下载链接)，如以及提及一些新的、流行的部署技术.
UPDATE, Aug.2018, a new and shorter option: How to create windows installer. Focused on summarizing
MSI and its major benefitsand to list themajor tools available(with download links), as well asmentioning some new, trending deployment technologies.
<小时>
我在软件开发部门担任过发布经理、构建工程师、设置开发人员和应用程序打包员大型企业中的强>、SOE 工程师和部署工程师 (SCCM).
I have worked in software development as a release manager, build engineer, setup developer and as an application packager, SOE engineer and deployment engineer (SCCM) in large corporations.
一路上，我使用了大部分主要的打包工具(有些有许多不同的版本):InstallShield、Wise(不幸的是不在市场上)、WiX、高级安装程序(只是测试)，Orca 我已经测试了 其他一些工具(链接到Windows Installer Authoring Tools for Developers"" 来自 http://www.installsite.org - 相当详尽的工具列表).我还使用了不太常见的打包和部署工具，例如 Computer Associates Unicenter——现在可能已经不在市场上.还有一个关于非MSI安装创作工具的页面.
Along the way, I have used most of the major packaging tools (some in many different versions): InstallShield, Wise (off market, unfortunately), WiX, Advanced Installer (just testing), Orca and I have tested some other tools (link to "Windows Installer Authoring Tools for Developers" from http://www.installsite.org - a rather exhaustive list of tools). I have also used less common packaging and deployment tools such as Computer Associates Unicenter - probably off market by now. There is also a page on Non-MSI Setup Authoring Tools.
更新:如果您发现自己需要一个 MSI 工具来比较两个 MSI 文件版本，或者只是为了从 MSI 文件中提取信息，您可能需要阅读以下答案:如何比较两个(或更多)MSI 文件?(专注于免费的 MSI 工具).
UPDATE: If you find yourself in need of an MSI tool for comparing two MSI file versions, or just to extract information from an MSI file, you might want to read this answer: How can I compare the content of two (or more) MSI files? (focused on free MSI tools).
这篇博文概述了一些不同创作工具的优点以及需要注意的一些问题.尽管有很多相似之处，但这些工具实际上却大不相同.我们已尽一切努力使描述尽可能客观 - 用积极和消极的方式描述现实世界的体验.
This post provides an overview of the strong points of some of the different authoring tools as well as some snags to be aware of. For all their similarities, these tools are actually quite different. All attempts have been made to make the descriptions as objective as possible - describing real world experience with positives and negatives.
- 在深入研究不同工具之前，这里有一些其他链接，其中包含有关 MSI 技术本身的信息.
- 这里是对部署工具中普遍支持的部署任务，以及为什么部署似乎变得越来越复杂的描述.
- 很多人似乎认为 MSI 的麻烦多于其价值，有时这是可以理解的.好处是实实在在的——尤其是对于企业部署而言，但也存在一些问题.
- 这是我写的关于MSI 的主要企业优势(来自 serverfault.com).这篇文章增长了太多，但希望仍然具有相关性.
- 在我写的关于典型的同一篇文章中MSI 文件中的实际设计缺陷(一项正在进行的工作 - 只是经历软件双方"的内存转储":开发和部署).
- 功能丰富.
- 始终掌握最新技术.
- (设置)面向开发人员.
- 提供不同版本.
- 旗舰产品 AdminStudio 提供了面向安装开发者的工具以及面向重新打包者的工具.
- 对于复杂产品，发布管理可能是 InstallShield 的主要卖点.您可以使用发布标志和类似结构轻松提供各种风格:语言版本、oem 版本、查看器、应用程序版本等.
- 发布标志主要用于有条件地从每个编译设置中排除或包含产品的某些部分 - 这通常是制作专业设置系列时要求的很大一部分.莉>
- Installshield 中的发布视图允许您全面了解所有不同的设置类型和版本.您会看到所有语言版本和为网络(一个大型设置文件)或可再分发媒体(外部源文件)以及您提供的任何其他风格提供的发布设置.
- 对于每个版本和版本至关重要的是，您可以覆盖重要设置，例如产品名称、产品版本、软件包、产品和升级代码以及许多其他必须根据动态更改的必需设置产品版本和语言版本.
- 在许多其他产品中，这种类型的发布和版本管理可能更难实施.对于更简单的设置，这种灵活性可能不太重要.
- For complex products release management is perhaps the main selling point for InstallShield. You can deliver flavors of all kinds with ease: language versions, oem versions, viewers, application editions, etc... using release flags and similar constructs.
- Release flags are essentially used to conditionally exclude or include certain parts of the product from each compiled setup - this is often a large part of what is asked for when making professional families of setups.
- The release view in Installshield allows full overview of all your different setup types and editions. You see all language versions and release setups delivered for the web (one large setup file) or for redistributable media (external source files) and whatever other flavors you have delivered.
- Crucially for each release and edition you can override important settings such as product name, product version, package-, product- and upgrade code as well as many other required settings that must dynamically change based on product edition and language version.
- In many other products this type of release and edition management can be much harder to implement. For simpler setups this type of flexibility might be less important.
- 还有命令行构建模块(用于专用构建服务器).
- 使用常规 VBScript/VBA/Javascript 自动化可以轻松实现一整套产品和版本的完全自动化构建.
- There are also command line build modules (for use on dedicated build servers).
- Full automation of the builds of a whole suite of products and editions is easily possible using regular VBScript / VBA / Javascript automation.
- 还提供了多种语言的现成基础对话框(额外收费).
- 您只需要本地化您自己的设置内容(功能列表标题、任何自定义对话框或消息框、带有文本的图像等...) - 仍有大量工作要做.
- 您可以提供大量的多语言设置.由于多种原因(阅读本地化部分)，我不建议这样做.最糟糕的问题是，您必须先以所有语言本地化所有新的和更改的内容，然后才能交付英文版本.这对于营销/销售来说几乎是不可接受的.并且总是有一些修复需要您重新构建和重新发布一种语言，然后您希望在没有所有其他语言的 UAT 和 QA 的情况下这样做.最好为每种语言提供单独的构建版本(易于实现).
- The base dialogs are also provided ready-made in a number of languages (costs extra).
- You only need to localize your own setup content (features list captions, any custom dialogs or message boxes, images with text, etc...) - still a lot of work.
- You can deliver a huge multi-lingual setup. This is not recommended in my experience for several reasons (read localization section). The worst problem is that you must localize all new and changed content in all languages before you can deliver the English version. This is almost never acceptable for marketing / sales. And there are always fixes that require you to rebuild and re-release a single language, and then you want to do so without UAT and QA for all other languages. It is better to provide separate builds for each language (easily implemented).
- 非常强大.有点复杂.
- 底层 MSI 技术的 GUI 功能的限制会导致一些障碍和恼人的限制，但这对于所有部署工具都是一样的.
- 根本原因是 MSI GUI 是使用 MSI 文件本身内部的数据表实现的，与正确的 Win32 对话框的完整事件模型"相比，这会导致对对话框事件的严重限制.
- Installscript 现在编译为本机 - 或者用它自己的沙箱模拟，不确定是哪个.无需像以前那样安装运行时.
- 顺便说一下，由于运行时损坏 - 似乎经常与 DCOM 相关 - 以及两者之间的各种不兼容性，此运行时是一些相当麻烦的部署问题的根源不同的运行时版本.以下是一些用于遗留目的"的故障排除链接:
- 无法安装 InstallShield Scripting Run Time.
- 安装程序无法找到或更新 ISScript.msi.
- Flexera Consumer Central(针对最终用户设置问题).
- Installscript now compiles to native - or emulated with its own sandbox, not sure which. There is no need to install a runtime like you had to before.
- Incidentally this runtime was the source of some rather troublesome deployment problems due to runtime corruption - seemingly often DCOM related - and various incompatibilities between different runtime versions. Here are some troubleshooting links for "legacy purposes":
- Unable to Install InstallShield Scripting Run Time.
- Setup Is Unable To Find or Update ISScript.msi.
- Flexera Consumer Central (for end user setup issues).
- 对于如此困难的技术来说非常重要.
- 通常非常有帮助 - 特别是在处理常见任务时.
- 公平地说，大多数错误都与特殊的Installscript MSI"项目类型有关，该项目类型为 MSI 设置实现了自定义对话框模型(而不是被抑制的基于表格的本机 GUI).
- 换句话说，Installscript MSI 项目类型不得在任何情况下使用.请牢记这一点，如果您仍在使用它们 - 它们特别难以正确升级(第一次部署可能没问题，但升级会中断).其他项目类型似乎运行良好.
- 在放弃 Installscript MSI(大多数人似乎都这样做)之后，该工具对我个人来说效果很好(虽然不是没有错误).
- In fairness most bugs relate to the special "Installscript MSI" project type that implements a custom dialog model for MSI setups (rather than the native, table based GUI which is suppressed).
- In other words, the Installscript MSI project type MUST NOT be used under any circumstance. Please take this to heart, if you still use them - they are particularly hard to upgrade properly (first time deployment might be OK, but upgrades are breaking). Other projects types seem to work well.
- After abandoning Installscript MSI (which most people seemed to do), the tool worked quite well for me personally (not bug free though).
- 与普通应用程序相比，允许一些新的东西.
- 应用程序流式传输 - 无需在机器上进行本地安装 - JIT.
- 在同一台计算机上使用两个不兼容的软件.
- 通过服务器更新.
- 控制许可 - 最大并发用户数或将软件绑定到一个组/用户.
- 快速轻松地向用户展示应用程序.
- 点击此处了解更多 Microsoft 营销.
Wise 正式退役，不过之前已经复活了.不幸的是 一些法律问题 这一次可能已经确定了 - 据我所知.对于这样一个伟大的工具来说，这将是一种耻辱.它被 Altiris 收购，然后又被赛门铁克收购.现在看起来是 场外.我还在总结好 Wise 的功能:
Wise is officially retired, but it has been resurrected before. Unfortunately some legal issues may have made it final this time - for all I know. That would be a shame for such a great tool. It was acquired by Altiris, and then Symantec. It now appears to be off market. I am still leaving in the summary of the good Wise features:
- 快速简便且功能丰富.
- 总体上非常易于使用，功能集出色.
- 缺少一些(非常)高级功能，例如 IIS、高级版本管理等...
- 比 Installshield 专注的代码更少.
- 功能独特且灵活的图形脚本编辑器.
- 精心设计的设置配置 GUI.
- 对于不同 MSI 文件的二进制差异，我尝试过的其他任何工具都无法与 Wise 接近.
- 差异查看器的易用性和清晰度简直太棒了.
- 对于企业包装而言，此类差异功能可能是工作中非常重要的一部分，因为您需要在许多不同版本中管理数百甚至数千个不同的软件包.
- 遗憾的是，该工具不再可用.
- 我们总是可以希望重生"(我在其他一些工具中看到过类似 Wise 的 GUI 片段).
- 最大的优点是文本源文件.无需将源代码存储为二进制文件，在这种情况下几乎不可能跟踪更改并进行适当的版本控制.
- 在分支、版本控制和合并方面，适当的文本来源对开发团队来说意义重大.这是一个巨大的飞跃(在我看来，特别是对于大型公司的内部开发 - 流程复杂、周转速度快且开发人员众多).
- 需要和使用文本源文件是创建 WiX 工具包的核心.这是快速且不完整的WiX 历史记录"，其中包含更多详细信息.推荐阅读以了解 WiX 的基础和原理.
- 某些将安装程序存储为二进制文件的部署工具最终可能会出现二进制源会出现永远无法正确追踪的神秘问题的情况.
- 这种情况尤其发生在工具更新之后，工具更新也会更新源中的格式(无论出于何种原因).
- 升级通常会影响数十个表和数百条记录，因此很难有效追踪真正的问题.
- 症状包括突然出现构建缓慢、安装速度突然变慢、无法解释的编译错误，甚至文件完全损坏等......
- 使用 WiX，您可以完全透明且精简"您的来源.如果做得好，它会更干净、更可靠，并且源的自动更新是可能的，但不会导致通过数十个 MSI 表进行级联更改.结合源代码管理更改可以轻松跟踪和(希望)理解 - 没有添加神秘的、未记录的内容.
- 尽管如此，必须指出的是，从 WiX 3 升级到 WiX 4 源文件似乎并非微不足道.让我们希望这是一次性的情况.老实说，我不确定为什么会发生这种情况，我也没有关于它的最新信息.
- 也许可以直接从 Rob Mensching 的博客中查看真实新闻:http://robmensching.com/blog/和 Bob Arnson 的博客 https://www.joyofsetup.com/.互联网使之成为可能，直接从马嘴里说出来 - 它有时是一个美妙的世界;-).有传言说他们正在做海龟一路向下".
- The big plus is the text source files. There is no need to store the source as a binary where it is almost impossible to track changes and do proper version control.
- Proper text sources make all the difference for development teams in terms of branching, versioning and merging. It is a quantum leap (in my opinion particularly for in-house development in large corporations - where process is complex, turnaround is quick and there are many developers).
- The need for and use of text source files was central to the creation of the WiX toolkit. Here is a quick and incomplete "WiX history" with more details. Recommended read to grasp the foundation and rationale for WiX.
- Some deployment tools that store the installer as binaries could end up in situations where the binary source would exhibit mysterious problems that could never be tracked down properly.
- This happened particularly after tool updates which also updated the format in the source (for whatever reason).
- The upgrades would often affect dozens of tables and hundreds of records making it an impossible task to track down the real problem effectively.
- Symptoms included things such as the sudden onset of slow builds, sudden slow installation speed, unexplainable compilation errors, even total file corruption etc...
- With WiX you have full transparency and "leanness" for your source. It is just cleaner and more reliable when done right and automatic updates of the source is possible, but won't cause cascading changes through dozens of MSI tables. Combined with source control changes are easily tracked and (hopefully) understood - no mysterious, undocumented stuff added.
- With all that said it must be noted that upgrading from WiX 3 to WiX 4 source files appears to not be trivial. Let's hope this is a one-time situation. I am not sure why this has happened to be honest, and I don't have up to date information about it.
- Perhaps check for real news straight from Rob Mensching's blog: http://robmensching.com/blog/ and Bob Arnson's blog https://www.joyofsetup.com/. Straight from the horse's mouth as the Internet makes possible - it is a wonderful world at times ;-). Rumor has it they are doing "turtles all the way down".
- 对于那些在其他工具中长期存在、间歇性、无法解释的错误而苦苦挣扎的人来说，这是天赐之物.{战争故事已删除}.
- 更好的是:问题实际上似乎在 WiX 中得到了解决，有时需要社区帮助 - 这对于开源工具包来说是合适的.但在大多数情况下，核心团队似乎会处理它.
- 需要时间来适应，即使您已经习惯了，事情也可能繁琐"地做好(特别是如果您没有正确使用所包含的帮助工具).
- 使用 dark.exe 反编译工具将现有的 MSI 文件反编译为 WiX XML 很有帮助.这使您可以在事先不了解太多的情况下研究 WiX 源.
- 针对复杂事物的出色可定制性，例如 IIS、COM+、SQL Server、权限、防火墙规则等...一切"都是可能的，但有时会涉及一些.
- WiX 有效地扩展了 Windows Installer"，提供了新的和急需的功能.对于以前不得不推出自己的"解决方案的每个人来说，这都是一个巨大的好处 - 通常用于看似微不足道的事情(但仍然很容易出错).
- 这些扩展的力量不容小觑.您可以摆脱许多自行编写的复杂自定义操作，转而使用经过测试的解决方案.适当的回滚支持！(供应商设置中的一个非常被忽视的功能 - 根据我的经验，几乎所有功能 - 在中止设置后导致不干净的系统状态).
- 我个人有编写 C++ dll 的经验，其中包含针对常见任务的自定义操作以及适当的回滚支持，工作量惊人 - 尤其是实际回滚功能的 QA.
- Takes time to get used to, and even when you are used to it things can be "fiddly" to get right (particularly if you don't use the included helper tools properly).
- It helps to use the dark.exe decompiler tool to decompile existing MSI files to WiX XML. This allows you to study the WiX source without knowing too much about it beforehand.
- Exceptional customizability for complex things such as IIS, COM+, SQL Server, permissioning, firewall rules, etc... "Everything" is possible, but somewhat involved at times.
- WiX effectively "extends Windows Installer" with new and much needed functionality. This is a massive benefit for everyone who previously had to "roll their own" solutions - often for things that seemed trivial (but was still very error prone).
- The power of these extensions can not be overstated. You can get rid of a lot of self-written, complex custom actions in favor of tested solutions. With proper rollback support! (a much neglected feature in vendor setups - in my experience almost all of them - causing unclean system state after aborted setups).
- I have personal experience writing a C++ dll with custom actions for common tasks with proper rollback support, and the amount of work was staggering - especially the QA of the actual rollback feature.
- 事情似乎正在改善，也许试试这个简短的总结.
- 一个有趣的项目可能是 IsWiX.值得一试.
- WiX 教程:https://github.com/iswix-llc/iswix-tutorials
- YouTube 快速演示:https://www.youtube.com/watch?v=nnV_OU6fk8c
- Things seem to be improving, perhaps try this short summary.
- An interesting project might be IsWiX. It is worth checking out.
- WiX tutorials: https://github.com/iswix-llc/iswix-tutorials
- Quick Youtube demo: https://www.youtube.com/watch?v=nnV_OU6fk8c
- 显然，对于 WiX 4 将支持哪些版本的 Visual Studio 会有一些限制.
- 我还没有详细信息，但您需要最新版本的 Visual Studio.我认为 Rob 和 Bob 有很多关于这方面的好博文.
- 社区":https://github.com/wixtoolset.和开放问题:https://github.com/wixtoolset/issues/issues
- 工具包下载也包括 DTF(部署工具基础)..NET 类，用于通过自动化处理 MSI 文件的所有内容.请参阅此处内嵌示例.非常有用，质量很好.无需处理 COM 互操作.请参阅此 serverfault.com 帖子.还有 Chris Painter 的博客.
- The "community": https://github.com/wixtoolset. And the open issues: https://github.com/wixtoolset/issues/issues
- The toolkit download includes DTF too (Deployment Tools Foundation). .NET classes for dealing with all things MSI files with automation. See a sample inline here. Extremely useful and good quality. NO COM interop to deal with. See this serverfault.com post. And Chris Painter's blog.
- 对于基于示例的修补程序 试试这篇 The Code Project 文章，了解如何使用 WiX (WiX 3) 创建 MSI 文件的快速入门.这真的很简单(如果您了解 MSI，那是不言而喻的).
- 您还可以阅读此 WiX 堆栈溢出文章，了解更多快速入门技巧.
- 新的&推荐:显示在 Visual Studio 中创建新 WiX 项目时编译工作 MSI 文件所需的当前最小更改的 stackoverflow 答案:WiX 安装程序 msi 未安装使用 Visual Studio 2017 创建的 Winform 应用.
- 您还可以使用 WiX 的 dark.exe(MSI 反编译器)将现有的 MSI 文件反编译为正确的 WiX XML 格式，然后研究如何将其组合在一起.非常有用且具有教育意义 - 特别是对于高级功能.
- For sample based tinkerers try this The Code Project article for a quick-start in how to create MSI files with WiX (WiX 3). It is really simple (if you know MSI it is self-evident).
- You can also read this WiX Stack Overflow article for further quick-start tips.
- NEW & RECOMMENDED: A stackoverflow answer showing the current minimal changes needed to compile a working MSI file when creating a new WiX project in Visual Studio: WiX installer msi not installing the Winform app created with Visual Studio 2017.
- And you can use WiX's dark.exe (MSI decompiler) to decompile an existing MSI file to proper WiX XML format and then study how it fits together. Very useful and educational - especially for advanced features.
- 版本 3.1 已稳定发布(2017 年 5 月发布).坚如磐石.
- 第 4 版此时已经开发了八年(2017 年 8 月).
- 尚不清楚何时可以稳定发布.
- 这显然是一个非常重要的更新，需要对现有 WiX 文件进行大量修改才能成功使用.
- 目前我无法提供任何有关主要差异的详细信息.
- 第 3 版的稳定性和可靠性无疑得到了保留.
- Version 3.1 is stable and out (Released May 2017). Rock solid.
- Version 4 has been eight years in development at this point (August 2017).
- It is not clear when it will be available for stable release.
- It will apparently be a very major update that requires substantial rework to existing WiX files to use successfully.
- I can not provide any details on what the major differences are at this point.
- The stability and reliability of version 3 has no doubt been preserved.
- 我没有将其用于实际开发.
- 非常易于使用，漂亮的图形用户界面.
- 更新:
- 在开发测试安装期间，工具本身的集成日志非常好.非常令人印象深刻.
- 也可用于在其架构版"中企业重新包装.
- 功能丰富.编译各种设置并支持所有新技术(App-X、App-V 等...)
- 对 App-V 的支持似乎非常广泛.
- 可以导入许多其他工具的源文件(Installshield、Inno、Wix、Wise、NSIS、Visual Studio、Desktop Bridge 等...).未经我广泛测试.
- I have not used this for real development.
- Very easy to use, nice GUI.
- UPDATE:
- Extremely good integrated logging in the tool itself during development test installation. Very impressive.
- Also available for corporate repackaging in its "Architect edition".
- Feature rich. Compiles all kinds of setups and supports all new technologies (App-X, App-V, etc...)
- Support for App-V seems very extensive.
- Can import a number of other tools' source files (Installshield, Inno, Wix, Wise, NSIS, Visual Studio, Desktop Bridge, etc...). Not tested extensively by me.
- 逆戟鲸 是免费的 Windows SDK 工具，它允许打开、编辑二进制 MSI 文件并在一定程度上进行比较.它还允许其他操作，例如生成用于修改 MSI 文件的转换文件和一些其他技术操作.我一直喜欢安装和使用的基本工具.此处有更广泛的 Orca 段落 讨论了它的使用(朝底部看).您通常必须安装 Windows SDK 才能获得 Orca(只需安装最新版本并搜索该工具).
- 已推荐名为Super Orca"的免费工具对我来说，就像InstEd"一样.我只是简单地使用过它们，但它们看起来不错，而且它们比 Orca 更容易掌握(无需下载 Windows SDK).
- 还有许多其他工具.以下是来自 http://www.installsite.org 的工具列表，带有指示该工具是否仍在积极维护:http://www.installsite.org/pages/en/msi/authoring.htm(感谢 Phil Wilson 提供的链接 - 我无法恢复他的回答).莉>
- 我想我还可以包含一个指向维基百科的安装软件列表.
- Orca is the free Windows SDK tool which allows binary MSI files to be opened, edited and to a certain degree compared. It also allows other operations such as generating transform files for modifying the MSI files and some other technical operations. A basic tool that I always like to have installed and available. There is a more extensive Orca paragraph here discussing its use (look towards the bottom). You normally have to install the Windows SDK to get hold of Orca (just install the latest version and search for the tool).
- A free tool called "Super Orca" has been recommended to me, as has "InstEd". I have used them only briefly, but they look OK, and they are easier to get hold of than Orca (no Windows SDK to download).
- And there are also many other tools. Here is a list of tools from http://www.installsite.org with an indication whether the tool is still actively maintained or not: http://www.installsite.org/pages/en/msi/authoring.htm (with thanks to Phil Wilson for the link - I couldn't resurrect his answer).
- I suppose I can also include a link to wikipedia's list of installation software.
我不能直接推荐工具.但我想我可以做一些观察"并提供一些进一步的决策链接.
It is not my place to make direct tool recommendations. But I guess I can make some "observations" and provide some further links for decision making.
对于任何认真的内部开发团队，我建议使用 WiX.在其他工具易于使用的地方(这非常重要，有时是唯一重要的东西)，WiX 擅长于灵活性、可扩展性、稳定性和 XML 文本源文件的使用 - 需要处理一些问题.由于其免费许可证，每个开发人员都可以查看和编译源代码，并且可以轻松跟踪、恢复或批准更改.管理一个开发人员都更新单个 WiX 源的过程仍然存在挑战(与常规开发工作没有什么不同 - 没有什么是容易的).
For any serious in-house development team I would suggest WiX. Where other tools have ease of use (which is very important, and sometimes the only thing that is important), WiX excels in its flexibility, extensibility, stability and the use of XML text source files - with the penalty of being somewhat involved to deal with. And due to its free license every developer can view and compile the source and changes are easily tracked, reverted or approved. Managing a process with developers all updating a single WiX source still has its challenges though (no different from regular development work - nothing is easy).
对于公司重新打包(诚然，这有点超出了stackoverflow.com 的开发人员关注点)我想目前的主要选择是Flexera AdminStudio 和高级安装架构师.还有其他产品可用，installsite.org 一如既往地提供详细信息:工具:重新包装 &企业部署.
For corporate repackaging (which admittedly is a little beyond the developer focus of stackoverflow.com) I guess the major options at the moment are Flexera AdminStudio and Advanced Installer Architect. There are also other products available, and as always installsite.org has details: Tools: Repackaging & Corporate Deployment.
对于小型开发团队来说，他们正在寻找一种快速简便的方法来部署他们的应用程序，我猜Installshield和Advanced Installer是最常见的基于 GUI"的工具.它们提供了许多功能，您将能够快速交付设置.如前所述，有时这是唯一重要的事情.事实上很多时候.但是，可以使用 WiX 来提供出色的安装程序 - 但需要更多的知识.有一个学习曲线，也有一些严重的限制——特别是在目前的 GUI 方面——但基础技术是非常可靠和免费的.重要的是，还有许多其他工具(来自 http://www.installsite.org 的列表)以及可能更适合您的任务 - 特别是如果它是一个简单的应用程序，只需要基本的部署功能.It is "unfair" that I haven't provided more information about these tools that are quite capable, but less commonly used or established.
For small development teams looking for a quick and easy way to deploy their applications, I guess Installshield and Advanced Installer are the most common "GUI based" tools. They provide a lot of features, and your will be able to deliver a setup quickly. As already stated, sometimes this is the only thing that is important. Very often in fact. It is, however, possible to deliver a great installer using WiX instead - but a lot more knowledge is required. There is a learning curve, and there are some severe limitations - particularly with regards to GUI at the moment - but the base technology is very solid and free. And importantly there are many other tools (list from http://www.installsite.org) as well that may be more appropriate for your task - particularly if it is a simple application that just needs basic deployment features. It is "unfair" that I haven't provided more information about these tools that are quite capable, but less commonly used or established.
I should make it clear that I recommend WiX for corporate teams delivering in-house applications because they can use the flexibility provided by WiX and they will also have the available expertise and technical skill to deal with the complexity of WiX. And they can train new guys when needed. A very important issue. WiX is not trivial to learn unless you already have a lot of Windows Installer knowledge - then it is a piece of cake, but still takes time because it is so flexible and for lack of a better word: "fiddly" - it is like real development, you got real control but need to be precise. Once set up a WiX source can be a dream to deal with - you know what is going on.
I should make it clear that I recommend WiX for corporate teams delivering in-house applications because they can use the flexibility provided by WiX and they will also have the available expertise and technical skill to deal with the complexity of WiX. And they can train new guys when needed. A very important issue. WiX is not trivial to learn unless you already have a lot of Windows Installer knowledge - then it is a piece of cake, but still takes time because it is so flexible and for lack of a better word: "fiddly" - it is like real development, you got real control but need to be precise. Once set up a WiX source can be a dream to deal with - you know what is going on.
To summarize: if you are a small (or large) third party vendor looking for a good way to get your application delivered quickly to your customers you are probably better off with a commercial tool aiming to provide ease of use and a quick solution to implement limited amounts of changes. For IIS, in particular, commercial tools have failed to provide the flexibility needed for me in the past. And in-house development teams should at least try WiX out.
To summarize: if you are a small (or large) third party vendor looking for a good way to get your application delivered quickly to your customers you are probably better off with a commercial tool aiming to provide ease of use and a quick solution to implement limited amounts of changes. For IIS, in particular, commercial tools have failed to provide the flexibility needed for me in the past. And in-house development teams should at least try WiX out.
Finally a word of caution: Advanced Installer, InstallShield and
Wisegenerally allow packaging of software for virtualization. I am not aware of any features in WiX for this as of now. Please add comments or just edit this post if you have information here.Finally a word of caution: Advanced Installer, InstallShield and
Wisegenerally allow packaging of software for virtualization. I am not aware of any features in WiX for this as of now. Please add comments or just edit this post if you have information here.I generally use other tools for prototyping and WiX for implementation if I have a choice. You can use WiX's dark.exe (MSI decompiler) to decompile an existing MSI file. Sometimes I implement something in Wise or InstallShield, compile an MSI and decompile it to WiX format. Then I lift the WiX markup and dump into my main WiX file. Works great and usually very fast. This in combination with the heat.exe tool for automatic component creation enabled me to package a huge IIS web site in less than 10 minutes after some practice runs. Afterwards I have the full customizability provided by WiX, with the ease of use of the other tools.
I generally use other tools for prototyping and WiX for implementation if I have a choice. You can use WiX's dark.exe (MSI decompiler) to decompile an existing MSI file. Sometimes I implement something in Wise or InstallShield, compile an MSI and decompile it to WiX format. Then I lift the WiX markup and dump into my main WiX file. Works great and usually very fast. This in combination with the heat.exe tool for automatic component creation enabled me to package a huge IIS web site in less than 10 minutes after some practice runs. Afterwards I have the full customizability provided by WiX, with the ease of use of the other tools.
Cleaning up the decompiled source is no picnic, but it is not rocket science either. Some MSI knowledge is needed and you will be "fiddling" for a while. Be aware that downloading trial versions of commercial tools to generate and decompile an MSI file is not recommended. The resulting MSI files are generally "watermarked" with features that are hard to remove.
Cleaning up the decompiled source is no picnic, but it is not rocket science either. Some MSI knowledge is needed and you will be "fiddling" for a while. Be aware that downloading trial versions of commercial tools to generate and decompile an MSI file is not recommended. The resulting MSI files are generally "watermarked" with features that are hard to remove.
Some Links:
这篇关于使用什么安装产品?InstallShield、WiX、Wise、高级安装程序等的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
