Installshield 或 Wix [英] Installshield or Wix

问题描述

我有一个使用 asp.net 3.5 开发的相当大的 web 应用程序，我需要准备一个安装程序包，用于在 IIS 6 和 7 上部署应用程序.我对 Wix 和 Installsheild 2010 做了很多研究(亲)并在做出决定之前需要一些建议.我注意到 installsheild 在许可证方面的费用很高，但对我来说，我有足够的预算，所以这不会成为问题.安装程序应该能够执行以下过程.

I have a pretty huge web application developed using asp.net 3.5 and I need to prepare an installer package which will be using to deploy the application on IIS 6 and 7. I have done a lot of research on Wix and Installsheild 2010 (pro) and need some advice before making decision. I notice that the installsheild is quite expense in terms of license but for me, I have enough budget so that won't be an issue. the installer should be able to perform the following processes.

• 部署已发布的网络资源(aspx 等).

• Deploy the published web resource (aspx etc).

创建虚拟目录.

在sql上创建数据库服务器并运行一些初始化脚本.

Create Database on sql server and run some initializing scripts.

修改 XML 文件和web.config 文件.

Modify XML files and web.config files.

设置允许写信给虚拟目录中的文件.

Set the permission to allow writing to the files in the virtual dir.

我发现这两种技术都能够完成上述场景，但我想获得个人经验和建议.

I found that both technologies are capable of doing the above scenarios but I would like to get personal experience and advices.

推荐答案

根据我使用 Wix 和 InstallShield 的经验，我建议使用 InstallShield，除非您需要一个相当基本和直接的安装程序.我这样说是因为缺乏可用的信息使巨大的 Wix 学习曲线变得更加困难

Based on my experience with Wix and InstallShield, I would recommend using InstallShield unless you need a fairly basic and straightforward installer. I say this because the huge Wix learning curve is made even more difficult by the lack of information available

没有关于 Wix 的书籍，因此您的资源仅限于Wix 教程，它详细而冗长，但仍然没有涵盖基础知识和您通过 Google 找到的博客文章.诚然，有很多很好的博客文章详细说明了如何完成特定的事情，但除非您没有截止日期，否则您可能无法一次坐几天研究如何在 Wix 中完成特定的事情.就我个人而言，我发现自己这样做太多了，Wix 无法成为一个可行的解决方案(同样，除非您只需要一个简单的安装程序)

There are no books on Wix, so your resources are limited to the Wix tutorial, which is detailed and lengthy but still doesn't cover much beyond basics, and blog posts you find via Google. Granted, there are many good blog posts which detail how to accomplish specific things, but unless you don't have deadlines to meet, you probably can't afford to sit and research how to do specific things in Wix for days at a time. Personally, I found myself doing this way too much for Wix to be a feasible solution (again, unless you only need a simple installer)

最终，就我而言，我们拥有使用 InstallShield 开发的现有安装程序，我们可以使用它更快地提高工作效率.InstallShield 也有自己的脚本语言，其中也有很好的文档.

Ultimately, in my case, we had existing installers which were developed with InstallShield and we are simply able to be productive quicker with it. InstallShield also has its own scripting language which has pretty good documentation too.

对我来说另一个重要的好处是 InstallShield 减轻了多个实例的痛苦(尝试搜索如何使用 Wix 执行此操作，您将了解我在说什么)和升级/修补.与在 Wix 中完成的任务相比，我使用 InstallShield 在一小部分时间内完成了这两个任务(尤其是多个实例).

Another big plus for me was that InstallShield eases the pain of multiple instances (try searching for how to do this with Wix and you'll get an idea of what I'm saying) and upgrading/patching. I was able to accomplish both of these (especially multiple instances) in a fraction of the time with InstallShield than what it took to accomplish in Wix.

我的建议是根据您的时间限制/截止日期/承诺、安装程序的复杂性和产品的成熟度进行选择.Wix 需要大量研究 InstallShield 提供了一种相当快速的方法.如果您拥有成熟的产品而不是相当年轻的产品，这可能会更加痛苦.

My advice would be to choose based upon your time constraints/deadlines/commitments, complexity of your installer, and maturity of your product. Wix requires LOTS of research for things InstallShield provides a fairly quick way of doing. This can be even more painful if you have a mature product versus a fairly young product.

希望这会有所帮助.

这篇关于Installshield 或 Wix的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！