Chained MSI's are run at the very end of the installation - you'll see in the execute sequence an action called "ISChainPackageCommit". This action prepares the chained MSI to run via a custom action - but it is not actually launched until after "InstallFinalize".
You can see this behavior if you create an MSI install log and you can see when the chained MSI is actually started.
The one last place you could place your custom action could be on the "Finish" button of the "SetupCompleteSuccess" dialog. Care must be taken that access to whatever data the custom action requires is available at such a late stage in the installation.
Chained MSI's are run at the very end of the installation - you'll see in the execute sequence an action called "ISChainPackageCommit". This action prepares the chained MSI to run via a custom action - but it is not actually launched until after "InstallFinalize".
You can see this behavior if you create an MSI install log and you can see when the chained MSI is actually started.
The one last place you could place your custom action could be on the "Finish" button of the "SetupCompleteSuccess" dialog. Care must be taken that access to whatever data the custom action requires is available at such a late stage in the installation.
