A question about embedded msi's and the queueing of commands

[rentzk]

Our program installs a 3rd party package and then creates a shortcut to one of it's components. The 3rd party package is provided to us in an msi which we call. We then need to read a registry value that this package sets in order to determine how to create the shortcut. At what point can we be certain that this registry value has been set? Can we check for this value after we install their msi package, or do we need to wait until after we call apply install?

We also have another 3rd party program that we may be including. This one however, is embedded in a normal installer exe. Like the msi files above, when can we be certain that it's registry and directory structures are actually on the system.

[MichaelNesmith]

When running 3rd party files:

(Un)Install MSI Setup: This command installs MSI files. It returns when the installation (or repair, removal, etc.) is complete.
Run Program/Run Program As: This command installs EXE files. It waits for the program being run to finish only if so desired on the command window (the wait flag).

For your own MSIcode script:

Purple Commands: These are native MSI database commands which take effect when Apply Install is being called.
All Others: These are direct execute commands, akin to MSI custom actions, which take effect immediately.