Our installer runs a bunch of post-install actions in which we start services and perform various initialization tasks. Per the user guide, I understand that by the time post-install actions are run, all installer files have been copied. So if an error occurs at this point, the error is reported and the remaining actions are skipped - but the install isn't actually aborted. The installer displays "Your installation has completed successfully" and exits with a return code of 0. Trouble is, our application isn't usable in this state - so we'd consider it a failed installation. Could we use an onErrorActionList to coerce a failure by firing an error action with a non-zero exitCode?
Please sign in to leave a comment.