Visual Studio安装程序项目是否适合复杂的安装程序? [英] Are Visual Studio Setup projects suitable for complex setups?
问题描述
是"Visual Studio设置"吗?适用于不同版本的复杂设置的项目?
Are "Visual Studio Setup" projects suitable for complex setups in different versions?
该应用程序相当大(> 500,000行代码)，并且正在不断开发中.每6到10个月发布一个新版本.我们有多个配置文件(INI和XML)，注册表项，数据库迁移脚本等.该应用程序正在从 Visual Basic 6.0 .旧的安装程序是使用 Installshield 构建的.对 Installshield 的反馈是:适应性差，重用性差-这就是为什么我们要评估"Visual Studio安装程序"作为替代.
The application is rather large (> 500,000 lines of code) and is under continuous development. Every 6 to 10 months a new version gets released. We have multiple configuration files (INI and XML), registry keys, database migration scripts, etc. The application is in the progress of being migrated from Visual Basic 6.0 to .NET. The old installer was build with Installshield. The feedback to Installshield is: Bad adaptability, bad reuse - that's why we are evaluating "Visual Studio Setup" as an alternative.
我们考虑的其他产品
- WiX
- NSIS
- Installshield (再次...)
- 明智
- 高级安装程序
- 缺少什么吗?
- Installshield (again...)
- Wise
- Advanced Installer
- Is Something missing?
我们不想考虑的解决方案:
Solutions we don't like to consider:
- Inno设置(感觉不对)
- Inno Setup (it just doesn't feel right)
推荐答案
否，否，否和否对Visual Studio部署项目.我去过大型"项目(15,000个文件，其中包含数千个合并模块和数百个InstallUtil自定义操作，因为VDPROJ几乎不暴露任何底层MSI(例如创建服务)).我可以花几个小时来研究它到底有多可怕.
No, no, no and no to Visual Studio Deployment projects. I've been there on "large" projects (15,000 files with thousands of merge modules and hundreds of InstallUtil custom actions because VDPROJ exposes almost nothing of the underlying MSI such as creating services). I could go on for hours about how horrible it truly is.
我有一个由四个安装开发人员组成的团队，我们混合使用 WiX 和 InstallShield .我们的典型安装具有近100个功能，800个合并模块和15,000个文件.我们几乎可以部署您可以想象的每种类型的资源，包括链接第三方安装以创建完整的产品或系统.我们能够针对十几个产品执行此操作，每个产品都建立在多个集成，发布和维护分支的基础上.我们四个人共同支持一个拥有约250名开发人员的400多人的组织.
I have a team of four installation developers and we use a mix of WiX and InstallShield. Our typical install has nearly 100 features, 800 merge modules and 15,000 files. We deploy nearly every type of resource you can imagine including chaining third-party installs to create complete products or systems. We are able to do this for over a dozen products each building off of multiple integration, release and maintenance branches. The four of us support an organization of over 400 people with around 250 developers.
我们之所以能够做到这一点，是因为InstallShield实际上可以为您提供大量的重用.您可以使用产品配置和功能/合并模块来创建文件和业务逻辑组的封装. WiX仍然做得更好(尽管要在这里和那里学习和发现漏洞仍然很困难，我们仍然需要InstallShield来解决)，因此我们一直在尽可能缓慢地将基准过渡到WiX.
We are able to do this because InstallShield actually can give you a fair amount of reuse. You use product configurations and features / merge modules to create encapsulations of groups of files and business logic. Still, WiX does a better job (although much harder to learn and feature holes here and there that we still need InstallShield for), so we have been slowly transitioning our baseline over to WiX where possible.
这篇关于Visual Studio安装程序项目是否适合复杂的安装程序?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
