Hello,
Is it correct to say InstallUISequence executes and then InstallExecuteSequence executes?
Actually the correct order is described in the picture from
this article. All the "Before File Installation" and "Before Finalization" standard actions execute twice(first and second phase) and at the end of the second phase("Execute installation script") the install returns to "ExecuteAction".
Does my Immediate execution Attached Custom Action execute before or after StartServices?
If your custom actions are set with "Immediate execution" they will be executed in the "Create installation script" phase when no modifcations are made to the machine. You should set them to "Deferred, with no impersonation" if you wish to execute them after the files are installed.
None of the files had been laid yet - not even the service. I'm surprised because StartServices happens after InstallFiles.
As I answered on your previous question, the files are not present because your custom actions are set to an "Immediate execution". As described in the above article, "Immediate execution" actions execute in the "Create installation script" phase and "Deferred" execute in the "Execute installation script" phase.
The files got installed between MsiPublishAssemblies and Install. What? They didn't get installed at InstallFiles. I'm not sure how my InstallServices works since that executes before the files get laid down. Why are they executing out of order (assuming they execute top-down)?
The files are not created during the "Create installation script" phase, they are created in the second phase when the script executes.
What is the different colored Standard Action icons communicating?
The difference is that the blue arrow standard actions do not end up in MSI. They are just an UI reference for the user when adding custom actions.
These are opposed to the lime arrow standard actions, which do have an action that can be traced in the built MSI.
Regards,
Mihai
FOLLOW US
Get the latest news in Application Packaging