Standard Actions |
|
Custom Action - Basic custom action |
|
Custom Action - In addition, the following custom action types are used with concurrent installations: |
||||||||
| ||||||||
Return Processing Options The concurrent installation session runs as a separate thread in the current process. A concurrent installation cannot run asynchronously. See Custom Action Return Processing Options. Execution Scheduling Options Options flags are available to control the potential multiple execution of custom actions. see Custom Action Execution Scheduling Options. In-Script Execution Options This custom action does not use this option. Return Values The return status of user exit, failure, suspend, or success from a concurrent installation is processed in the same way as any other action. Note however that Windows Installer translates the return values from all actions when it writes the return value into the log file. For example, if the action return value appears as 1 in the log file, this means that the action returned ERROR_SUCCESS. For more information about this translation see Logging of Action Return Values.Note that if a concurrent install has msidbCustomActionTypeContinue set, then a return of ERROR_INSTALL_USEREXIT, ERROR_INSTALL_REBOOT, ERROR_INSTALL_REBOOT_NOW, or ERROR_SUCCESS_REBOOT_REQUIRED is treated as ERROR_SUCCESS. This means that if you set msidbCustomActionTypeContinue and your concurrent installation requires a restart, the requirement for the restart will be ignored. Additionally, the error code from the concurrent installation custom action will be ignored.If msidbCustomActionTypeContinue is not set, the following return codes plus ERROR_SUCCESS are treated as success and have the following meanings. Other return codes are treated as failure. See Custom Action Return Values. Remarks A conditional expression is required to enable the concurrent installation at either installation or removal of the associated component or feature. | ||||||||
| ||||||||
Return Processing Options The concurrent installation session runs as a separate thread in the current process. A concurrent installation cannot run asynchronously.For more information, See Custom Action Return Processing Options. Execution Scheduling Options Options flags are available to control the potential multiple execution of custom actions. For more information, see Custom Action Execution Scheduling Options. In-Script Execution Options Not used. Return Values The return status of user exit, failure, suspend, or success from a concurrent installation is processed in the same way as any other action. Note however, that Windows Installer translates the return values from all actions when it writes the return value into the log file. For example, if the action return value appears as 1 in the log file, this means that the action returned ERROR_SUCCESS. For more information, see Logging of Action Return Values.Note that if a concurrent installation has msidbCustomActionTypeContinue set, then a return of ERROR_INSTALL_USEREXIT, ERROR_INSTALL_REBOOT, ERROR_INSTALL_REBOOT_NOW, or ERROR_SUCCESS_REBOOT_REQUIRED is treated as ERROR_SUCCESS. This means that if you set msidbCustomActionTypeContinue and your concurrent installation requires a restart, the requirement for the restart will be ignored. Additionally, the error code from the concurrent installation custom action will be ignored.If msidbCustomActionTypeContinue is not set, the following return codes plus ERROR_SUCCESS are treated as success and have the following meanings. Other return codes are treated as failure. See Custom Action Return Values. Remarks A conditional expression is required to enable the concurrent installation at either installation or removal of the associated component or feature. | ||||||||
| ||||||||
Return Processing Options The custom action type 39 fails if the application is not advertised or installed. To avoid this failure, you must set the msidbCustomActionTypeContinueflag.A concurrent install cannot run asynchronously. See Custom Action Return Processing Options. Execution Scheduling Options Options flags are available to control the potential multiple execution of custom actions. see Custom Action Execution Scheduling Options. In-Script Execution Options The custom action does not use this option. Return Values The return status of user exit, failure, suspend, or success from a concurrent installation is processed in the same way as any other action. Note however that Windows Installer translates the return values from all actions when it writes the return value into the log file. For example, if the action return value appears as 1 in the log file, this means that the action returned ERROR_SUCCESS. For more information, see Logging of Action Return Values.Note that if a concurrent installation has msidbCustomActionTypeContinue set, then a return of ERROR_INSTALL_USEREXIT, ERROR_INSTALL_REBOOT, ERROR_INSTALL_REBOOT_NOW, or ERROR_SUCCESS_REBOOT_REQUIRED is treated as ERROR_SUCCESS. This means that if you set msidbCustomActionTypeContinue and your concurrent installation requires a restart, the requirement for the restart will be ignored. Additionally, the error code from the concurrent installation custom action will be ignored.If msidbCustomActionTypeContinue is not set, the following return codes plus ERROR_SUCCESS are treated as success and have the following meanings. Other return codes are treated as failure. See Custom Action Return Values. Remarks A conditional expression is required to enable the concurrent installation at either installation or removal of the associated component or feature. |
Custom Action Return Processing Options. |
||||||||||||||||||||
|
Custom Action Execution Scheduling Options.
|
||||||||||||||||||||
|
Custom Action In-Script Execution Options. |
||||||||||||||||||||||||||||||||||||||||||||
|
Custom Action Patch Uninstall Option. |
||||||||
|
Custom Action NoImpersonate Option. |
||||||||
|
Logging of Action Return Values. |
||||||||||||||||||||||||||||||||||||||||
|
Custom Action Return Values. |
||||||||
|