Hi Stephan,
At first I built a merge module that has a property (all capitals, so should be "pubic" if it matters in that context). Then I made a configurable for that property (also in all capitals).
Then I built a "main" installer that includes this merge module. It sets the exported configurable of the merge module to the value of a non-public property of the main installer, for which the variable expansion doesn't work. Maybe things got a little bit clearer. I also hacked together a small example project if this should be needed. This shows a message box with the variable in it (Which is broken on install, too. I don't fully understand why.)
This seems to be an Advanced Installer issue. We'll investigate the problem and try to fix it in a future version of Advanced Installer, thank you for bringing it to our attention.
Maybe I was a bit unclear here. I added two merge modules to the main installer. One module has the other one as a prerequisite. I expected that all custom actions from the module which depends on the other get run after all actions of the dependency are finished.
This is the normal behavior, when a merge module is added in the Merge Module page of an installer project. So, the merge module will be integrated in the main installer and all its custom actions and all custom actions added in the main project will be executed in the order they are added in the Custom Actions page.
For example if the merge module has two custom actions (
"A" placed after "Install Execution Stage ->
Searches" action group and
"B" placed after "Install Execution Stage ->
Add Resources" action group) and the main installer has one custom action (
"C" placed under ""Install Execution Stage ->
Preparing" action group), at install time they will be executed in the following order:
A -> C -> B
You can read more about merge modules in our
Merge Module Page article.
Let us know if you have any other question.
Best Regards,
Eusebiu
FOLLOW US
Get the latest news in Application Packaging