Visual Studio Setup 项目是否适合复杂的设置? [英] 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 到 .NET.旧的安装程序是使用 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.
我们考虑的其他产品:
- Installshield(再次...)
- Wise
- 高级安装程序
- 有什么遗漏吗?
我们不喜欢考虑的解决方案:
Solutions we don't like to consider:
- Inno Setup(就是感觉不对)
- 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 个文件.我们部署了您能想象到的几乎所有类型的资源，包括链接第三方安装以创建完整的产品或系统.我们能够为十多种产品做到这一点，每个产品都建立在多个集成、发布和维护分支之上.我们四个人支持一个拥有 400 多人的组织和大约 250 名开发人员.
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 Setup 项目是否适合复杂的设置?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
