We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

stpwd
Posts: 3
Joined: Tue Jun 04, 2013 12:52 pm

How to set Properties for merge module?

Hi!
After I built an installer with merge modules in it I tried to set a exported property of the merge module to a value of a property of the main installer. Installing works fine, but uninstalling doesn't work (the variable of the merge module only gets expanded to the variable name of the variable from the main installer, not to the value). Setting the "persistent" option didn't help either.
How to fix this? What is the correct value of the persistent option (in the installer and in the merge module)?

Edit: A second question: When using multiple merge modules, the custom actions in the merge modules are run in parallel, not after one another. Is this the desired behavior?

Thanks,
Stephan
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: How to set Properties for merge module?

Hi Stephan and welcome to Advanced Installer forums.
After I built an installer with merge modules in it I tried to set a exported property of the merge module to a value of a property of the main installer. Installing works fine, but uninstalling doesn't work (the variable of the merge module only gets expanded to the variable name of the variable from the main installer, not to the value).
I'm afraid I don't fully understand what is your scenario. Can you give us more details about your scenario (maybe exemplify)?
Setting the "persistent" option didn't help either.
How to fix this? What is the correct value of the persistent option (in the installer and in the merge module)?
If you use the "Set persistent property" option, the property will be stored in the registry and will be available in maintenance mode (repair, uninstall, etc.).
Edit: A second question: When using multiple merge modules, the custom actions in the merge modules are run in parallel, not after one another. Is this the desired behavior?
Please keep in mind that all custom actions have a running order which you can find in the Table Editor page, "InstallExecuteSequence" table, "Sequence" column. Although, two custom actions can run in parallel if the "Wait for custom action to finish before proceeding" and "Wait for return code at the end of the sequence" options are not set for them in the Custom Actions page. This is also applying for custom actions added in a merge module.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
stpwd
Posts: 3
Joined: Tue Jun 04, 2013 12:52 pm

Re: How to set Properties for merge module?

Hi Eusebiu!

Thanks for your reply.
After I built an installer with merge modules in it I tried to set a exported property of the merge module to a value of a property of the main installer. Installing works fine, but uninstalling doesn't work (the variable of the merge module only gets expanded to the variable name of the variable from the main installer, not to the value).
I'm afraid I don't fully understand what is your scenario. Can you give us more details about your scenario (maybe exemplify)?
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 litte 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.)
My feeling is that I am missing something from the whole concept. I didn't find any good documentation on that matter.
What I'm trying to achieve is to get properties (both public and non-public) in the main installer to configure the merge modules from Advanced Installer and msiexec.
Edit: A second question: When using multiple merge modules, the custom actions in the merge modules are run in parallel, not after one another. Is this the desired behavior?
Please keep in mind that all custom actions have a running order which you can find in the Table Editor page, "InstallExecuteSequence" table, "Sequence" column. Although, two custom actions can run in parallel if the "Wait for custom action to finish before proceeding" and "Wait for return code at the end of the sequence" options are not set for them in the Custom Actions page. This is also applying for custom actions added in a merge module.
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.

Thanks,
Stephan
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: How to set Properties for merge module?

Hi Stephan,

Can you please send us an example project of the main installer and also examples of the two merge modules so we can investigate them and see where is the problem?

Best Regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
stpwd
Posts: 3
Joined: Tue Jun 04, 2013 12:52 pm

Re: How to set Properties for merge module?

Hi Eusebiu,

I just sent the two project files to support at adv...com.
FWIW: It's AI 10.2 Enterprise on Windows 8 64 Bit.

Thanks,
Stephan
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: How to set Properties for merge module?

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
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”