合并模块如何升级? [英] How merge module upgrades?

查看:21
本文介绍了合并模块如何升级?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我可以找到大量有关 msi 如何升级的信息.例如.有关次要升级、小升级、主要升级及其用例和限制的信息.但是,我找不到有关合并模块升级行为的信息,例如:

I can find plenty of info on how msi upgrades. E.g. info about minor upgrade, small upgrade, major upgade, and their use case and limitations. However, I cannot find info on the upgrade behavior of merge module, such as:

  1. 好像 msm 没有指定小、小或重大升级.那么它的方式表现在?是否卸载旧的首先版本或仅更新已更改文件?
  2. 有什么办法可以指定从哪个版本可以升级喜欢微信?
  3. 我可以添加/删除/重命名吗新版本的组件?
  4. 如果此 msm 的更新版本是已经安装和容器msi 决定安装,会吗用这个旧版本覆盖微信?

推荐答案

合并模块可以参与两种升级方案.第一种是安装程序升级时,它升级一个.msm 文件.这发生在像 Visual Studio 服务包这样的情况下,它们提供更新的合并模块供您使用.这可能会出现问题,因为 .msm 文件没有文件版本(即使它们有合并模块版本),因此文件版本控制规则不适用于.你可能不是在问这个案子.

There are two upgrade scenarios that a merge module can take part in. The first is when the installer is upgrading, and it upgrades a .msm file. This happens in cases like the Visual Studio service pack where they provide updated merge modules for you to use. This can be problematic as .msm files do not have a file version (even though they have a merge module version), so file versioning rules do not apply kindly. You're probably not asking about this case.

另一种情况是合并模块已合并到将升级的安装程序中.它不再是一个合并模块,而是它的文件和其他记录是消费安装程序的一部分.在这种情况下,它已合并到的 .msi 控制升级步骤.两者互动,告知您对前三个问题的答案.如果合并模块有不遵循次要升级规则的更改,那么消费安装程序将无法使用次要升级,而必须求助于主要升级.相应地,如果您想在消费安装程序中使用(或允许)小的升级,您必须小心您的组件.这可能比在 .msi 中更难,因为您无法在合并模块中添加新功能.文件版本控制规则将像在所有 Windows Installer 安装中一样适用;因此,您的第四个问题的答案是在逐个文件、逐个组件的基础上确定的,而不是对模块的全部内容进行分组回答.

The other scenario is when the merge module has been merged into an installer that will upgrade. It is no longer a merge module, but instead its files and other records are part of the consuming installer. In this case, the .msi into which it has been merged controls the upgrade steps. The two interact, informing your answers to your first three questions. If the merge module has changes that do not follow minor upgrade rules, then the consuming installer will be unable to use a minor upgrade, and must resort to major upgrades. Correspondingly if you want to use (or allow) minor upgrades in the consuming installer, you must be careful about your components. This can be harder than in an .msi since you cannot add new features inside a merge module. File versioning rules will apply just like they do in all Windows Installer installations; thus the answer to your fourth question is determined on a file-by-file, component-by-component basis instead of a group answer for the entire contents of the module.

这篇关于合并模块如何升级?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆