I have a Basic MSI deferred VBScript custom action in which I want to set a property that will be used in the installer in another custom action down the line. I know how to use customActionData to get properties that were set in Set Property custom actions, but how to set properties that can be accessed later (write to registry, write to a text file on the disk, what?)? Can you write to the SecureCustomProperties from the deferred custom action?
I'm not 100% positive, but I don't think you can set properties from a deferred custom action except for the very few that you still have direct access to.
There's no real MSI line of communication from a deferred action to another or back to immediate actions. One way to handle it is to pass a path to a temp file to the deferred actions via properties, and populate the contents of the file to be read by later actions who also know the path.
