MSI Packaging Guide

We handle packaging of our product / module combinations. Some of them are autonomous, some of them are interdependent. All versions must deploy side by side. Since we are considering two options:

  • One MSI per package and version
  • One MSI per product / module and version

The first option means that combinations of the same merge modules will be delivered in multiple packages. The second option is an easier way.

Can you provide some advice on this issue? Will any of the alternatives cause grief in the long run?

0


source to share


1 answer


If you install the same component twice, Windows Installer will simply refer to the first installation, so there isn't much difference between the two. If you already split your components into merge modules, you are guaranteed that the components will share their GUIDs, and you will get this behavior, and sharing the components will not cause any problems.



If you are making many small MSIs, however, multiple MSIs are needed to install the package, you will lose Windows Installer's transactional capabilities - a failed installation will not roll back the previous installation - and you should probably look at the chaining application. I usually try to do as little MSI as possible.

+2


source







All Articles