merge module, different versions

  • Thread starter Thread starter EP
  • Start date Start date
E

EP

Let's say I distribute an application through a merge module, which gets
consumed by other installers.

Let's say I've released a new version of the module, so now one installer
references v1 and another references v2.

How are the modules supposed to manage the different versions of the
files/applications/keys they contain?
 
This is really up to how you ahve authored the merge modules.

The merge modules version on helps out with the merging of the modules, it
is never used during an installation.

Do you need to have V1 and V2 on the same machine (i.e. two sets of files?)
or do you need V2 to upgrade V1?
 
In fact there is no upgrade of a merge module (as far I know). After merging
a merge module to a setup the merge module is "gone" and only the components
are known. The components follow the typical versioning rules (see MSI SDK).

Distributing an application via merge modules might be difficult if there
are "huge" changes within the merge module. Especially if the merge module
is installed by several setups on the same machine adding, removing and
changing components is rather dangerous.

Nested Setups (packed in merge modules) are no alternative anyway, as they
don't support upgrading.
 
Back
Top