7

An MSI installer calls a lot of pre-defined actions during install - FindRelatedProducts, CheckVersion, etc. Different actions are called during different install types and sequences: admin, unattended, user, execute, deffered... and custom actions are queued 'before' or 'after' these predefined MSI actions.

Is there a complete list available that shows the exact sequence in which MSI actions are called in different install modes and sequences? Ideally with short comments about what each action does and what is a good practice to insert custom actions into.

saschabeaumont
  • 22,080
  • 4
  • 63
  • 85
grigoryvp
  • 40,413
  • 64
  • 174
  • 277

2 Answers2

7

See the MSDN documentation, specifically the documentation on Using a Sequence Table.

For offline reference, download the Windows Installer 4.5 SDK and read MSI.CHM (it's much easier to navigate than the MSDN stuff anyway)

saschabeaumont
  • 22,080
  • 4
  • 63
  • 85
  • Look at the sequence table of the most simple installer you can imagine, that will show the default sequence for MSI files generated by that same tool under the same OS. It's not a simple set of defaults, it could vary based on inputs and API versions that were used in the build process. Without official publications, you need to work backwards unfortunately. – saschabeaumont Jul 12 '16 at 04:41
2

Windows Installer is very complex (after my experience with it I could say it is an euphemism for ridiculous mess) and I did not find any summary of required order of actions. However, the order for example in Suggested InstallExecuteSequence is suggested by MS, so it should work.

comodoro
  • 1,489
  • 1
  • 19
  • 30