管理 InstallScript 版本
如何管理 InstallScript 差异升级和发布。
对于我发布的每个版本，我需要保留两个版本吗？一种适用于现有客户 - 用于升级，另一种适用于新客户进行全新安装？
然后，随着产品继续其生命周期，我是否需要保留所有这些版本以便我可以创建差异升级？
这是公司处理发布的方式吗？似乎有很多数据需要保存和处理......
How to manage InstallScript differential upgrades and releases.
For every version I ship, do I need to keep two releases? One for existing customers - for upgrade and one for new customers for fresh install?
Then as the product continues its life cycle, Do I need to keep all those releases so that I could create a differential upgrade?
Is that the way companies handle their releases? seems like a lot of data to keep and handle...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
差异升级所节省的时间（时间或大小）值得这么麻烦吗？听起来对于这两种情况，发布完整的安装程序会容易得多。
无论您是否使用它们来创建差异版本，我都建议保留所有以前的版本。您永远不知道何时需要测试旧版本的行为，而唯一真正的方法就是使用其原始版本。
Are the savings (time or size) of differential upgrades worth this hassle? It sounds like it would be significantly easier to just release full the installer for both scenarios.
Whether or not you use them to create differential releases, I would suggest keeping all your previous releases around. You never know when you'll need to test the behavior of an old release, and the only real way to do that is with its original bits.
Installshield 基本上只是将所有文件移动到目标计算机的文件夹中。假设您要从版本 1.0 升级到 3.0。在升级到 3.0 之前，您的情况是否有必要升级到 2.0？还是真的可以直接放下3.0？除非您需要更新程序，否则没有任何意义。
我们的处理方式是，像您所说的那样，我们有两个版本。 “全新安装”和“更新程序”。不过，我们需要更新程序，因为在软件到达最新版本之前，我们需要为每个修补程序运行线性数据库迁移，因此我们不能只是“跳过”2.0
如果我们需要应用修补程序，我们会创建一个精简版本的更新程序直到下一个版本，我创建了另一个全新安装和更新程序。
Installshield basically just moves over all of the files to the target machine's folder. Lets say you are going from version 1.0 to 3.0. Is there any real point in your case to upgrade to 2.0 before going to 3.0? Or could you really just lay down 3.0 directly? Unless you NEED an updater, then there's no point in having one.
How we handle it, is that we have two build like you said. A 'Fresh install' and 'Updater.' We need the updater though, because we have linear database migrations that need to run for each hotfix before the software can reach the newest version, so we can't just "skip" that 2.0
If we need to apply a hotfix, we create a stripped down version of the updater until the next release, where I create another Fresh install and Updater.