使用什么安装产品？ InstallShield，WiX，Wise，Advanced Installer等 [英] 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 Compact Framework 3.5

• Progress 4GL
• Visual Studio 2005
• Visual Studio 2008
• .NET Compact Framework 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，8月。 2018 ，一个新的较短的选项： 如何创建Windows安装程序 。
专注于总结 MSI及其主要优点 ，并列出 主要可用工具 （具有下载链接），以及
和 提及了一些新的，流行的部署技术 。

UPDATE, Aug.2018, a new and shorter option: How to create windows installer. Focused on summarizing MSI and its major benefits and to list the major tools available (with download links), as well as mentioning 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.

一路走来，我使用了大多数主要的打包工具（有些版本很多）： < a href = http://www.installshield.com/ rel = noreferrer> InstallShield ， 明智 （在市场外，不幸的是）， WiX ， 高级安装程序 （正在测试）， Orca ，并且我已经测试过> 其他一些工具 （从开发人员的Windows Installer创作工具） > 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文件中的典型现实世界设计缺陷 （一项正在进行中的工作-只是内存转储 来自软件两面：开发和部署）。
  
  
  • Before delving into the review of the different tools, here are a few other links with information about the MSI technology itself.
  • Here is a general description of deployment tasks commonly supported in deployment tools, and a description of why deployment seems to become more and more complicated.
  • A lot of people seem to think MSI is more trouble than it is worth, and sometimes that can be understandable. The benefits are real - particularly for corporate deployment, but so are some of the problems.
    • Here is a description I wrote about the major corporate benefits of MSI (from serverfault.com). The article has grown too much, but is hopefully still relevant.
    • In the same article I wrote about typical real-world design flaws in MSI files (a work very much in progress - just a "memory dump" from experiencing "both sides of software": development and deployment).
    
    
    • 功能丰富。
    
    
    • 始终保持最新技术。
    
    
    • （设置）面向开发人员。
      
      
      
      
      • 提供不同版本。
      
      
      • 旗舰产品AdminStudio提供面向安装程序开发人员的工具以及面向重新包装程序的工具。
      
      
      • Feature rich.
      • Always up to date with latest technologies.
      • (Setup) Developer oriented.
        • Different editions available.
        • The flagship product AdminStudio provides both setup developer oriented tools as well as repackager oriented tools.
        
        
        • 对于复杂产品，发布管理可能是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脚本运行时。
              
              
              • 安装程序无法找到或更新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).
                
                
                • 对于如此困难的技术非常重要。
                
                
                • 通常非常有帮助-特别是在处理常见任务时。
                li>
                
                • Very important for such a difficult technology.
                • Often very helpful - especially for dealing with common tasks.
                
                
                • 公平地说，大多数错误都与特殊的 Installscript MSI 项目类型有关，该类型为MSI设置实现了自定义对话框模型（而是
                
                
                • 换句话说，使用 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营销。
                
                
                • Allows a few new things compared to a normal application.
                • Application streaming - no local installation on machines - JIT.
                • Use two incompatible software on the same computer.
                • Updating through the server.
                • Control licensing - maximum simultaneous users or tie software to a group / user.
                • Present the application quickly and easily to users.
                • More Microsoft marketing here.

                明智已正式退休，但之前已复活。不幸的是一些法律问题这次可能已经定案了，据我所知。对于如此出色的工具，这将是可耻的。它被Altiris和Symantec收购。现在它似乎是场外交易。我仍将保留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".
                          
                          
                          • 对于那些在其他工具中长期，间歇性，无法解释的bug感到困扰的人来说，这真是天赐之物。 {战争故事已删除}。
                          
                          
                          • 甚至更好：问题似乎实际上已经在WiX中得到解决，有时需要社区的帮助-这对于开源工具包来说是适当的。
                          
                          
                          
                          
                          • 花时间习惯，即使习惯了，事情也可以轻率地纠正（特别是如果您不使用）
                          
                          
                          • 它有助于使用 dark.exe反编译工具将现有的MSI文件反编译为WiX XML。这样一来，您就无需事先了解WiX源就可以对其进行研究。
                          
                          
                          • 对复杂事物的出色可定制性，例如 IIS ， COM + ， SQL Server ，许可，防火墙规则等...
                            一切都是可能的，但有时会涉及其中。
                          
                          
                          • 有效地使用WiX 扩展了Windows Installer ，并提供了许多新功能。对于以前不得不推出自己的解决方案的每个人来说，这都是一个巨大的好处-通常是针对那些看起来微不足道的事情（但仍然很容易出错）。
                          
                          
                          • 这些扩展的功能可以不要夸大其词。您可以摆脱许多自写的，复杂的自定义操作，而使用经过测试的解决方案。有了适当的回滚支持！ （在供应商设置中一个被忽略的功能-根据我的经验，几乎所有这些功能-在中止设置后都会导致系统状态不干净）。
                          
                          
                          • 我有个人的经验，使用通用的自定义操作编写C ++ dll具有适当的回滚支持的任务，并且工作量令人震惊-尤其是实际回滚功能的质量保证。
                          
                          
                          • 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版本会有一些限制。
                              
                              
                              • I还没有详细信息，但是您将需要Visual Studio的最新版本。我认为Rob和Bob都有很好的博客文章。
                              
                              
                              
                              
                              • 社区： https：// github。 com / wixtoolset 。还有公开的问题： https://github.com/wixtoolset/issues/issues
                              
                              
                              • 该工具包下载也包含DTF（部署工具基金会）。 .NET类，用于自动处理所有MSI文件。在此处查看内联示例。极其有用和优质。不需要 COM 互操作来处理。请参阅此serverfault.com帖子。还有克里斯·画家的博客。
                              
                              
                              • 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.
                              
                              
                              • 对于基于样本的修补匠 > 尝试此代码项目文章 ，以快速入门如何使用WiX创建MSI文件（WiX 3）。这真的很简单（如果您知道MSI，这是不言而喻的。）
                              
                              
                              • 您还可以阅读此WiX堆栈溢出文章以获取更多快速入门提示。
                              
                              
                              • 新品推荐：一个stackoverflow答案，显示了在Visual Studio中创建新的WiX项目时，编译工作的MSI文件所需的当前最小更改： 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.
                                  
                                  
                                  • 我没有将其用于实际开发。
                                  
                                  
                                  • 非常易于使用，很好的GUI。
                                  
                                  
                                  • 更新：
                                    
                                    
                                    
                                    集成日志记录。
                                    
                                    • 还可以在其 Architect版本中用于企业重新包装。
                                    
                                    
                                    • 功能丰富。编译各种设置并支持所有新技术（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.
                                      
                                      
                                      • Orca 是免费的Windows SDK工具，它允许打开，编辑二进制MSI文件，并在一定程度上进行比较。它还允许其他操作，例如生成用于修改MSI文件的转换文件和其他一些技术操作。我一直喜欢安装并可用的基本工具。这里有一个更广泛的Orca段落讨论了其用法（朝下看）。通常，您必须安装Windows SDK才能使用Orca（只需安装最新版本并搜索该工具）。
                                      
                                      
                                      • 一个免费工具，名为 超级逆戟鲸 已被推荐给我，而 InstEd 。我只是简单地使用过它们，但是它们看起来还不错，而且比Orca（没有Windows SDK下载）更容易掌握。
                                      
                                      
                                      • 还有许多 other工具。以下是 http://www.installsite.org 中的工具列表，指示该工具是否仍在积极维护中： http：// www .installsite.org / pages / en / msi / authoring.htm （感谢菲尔·威尔逊的链接-我无法让他复活）。
                                      
                                      
                                      • 我想我还可以包含指向 wikipedia的安装列表的链接软件 。
                                      
                                      
                                      • 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.

                                      这不是我提出直接工具建议的地方。 But I guess I can make some \"observations\" and provide some further links for decision making.

                                      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.

                                      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).

                                      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).

                                      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.

                                      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.

                                      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.

                                      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 Wise generally 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 Wise generally 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:

                                      
                                      
                                      • How to create windows installer
                                      
                                      
                                      • Shortlist of deployment tools
                                      
                                      
                                      • Older content
                                      
                                      

                                      这篇关于使用什么安装产品？ InstallShield，WiX，Wise，Advanced Installer等的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！