As per the response to my feature request, Advanced Installer currently doesn't support multiple HTTPS bindings in IIS. As a workaround I created a custom action that adds the binding.
However it seems that Advanced Installer executes all custom actions before it performs IIS configuration. Our setup creates the websites it needs, so at the time my custom action executes, the websites it wants to add bindings to don't yet exist. So the custom action never has any effect!
I currently have my custom actions setup to run as deferred in the Install Execution Stage, after the Add Resources step. I'm guessing that I might be able to get the desired behaviour if I move my action into the Finish Dialogs Stage, but that's not optimal because then the action can't be rolled back.
Is there any (recommended) way to get this custom action to run after IIS has been configured?