Merged Module not installed - Advanced Installer Community

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!

RedDrago
Posts: 33
Joined: Thu Jan 19, 2012 9:23 am

Merged Module not installed

Hello,

I have a problem with the Merged Modules, and as the topic tells, the basic problem is, that the modules are not beeing installed.

I'll try to explain what I whant to achieve and how I tried to implement it.

I'am using the modules because the application I want to install is split into several Editions. Each Edition reqires aditional files, which they share, but are not part of the core. I've put those files into independent modules. Every Edition that requires those modules, have dependencies on those those modules.

Example1: Edition 1 requires modules A, B AND D
Dependencies on modules A, B AND D

Example2: Edition 2 requires modules B AND C
Dependencies on modules B AND C

A Custom Action, which decrypts several values and sets several properties for each Edition, which is to be installed, to "1".

Every Edition has its own feature. Shared modules have their own features.
Since I want to install only the required files for each edition, I set conditions on every feature like for module B of the examples above: "E1 = 1 OR E2 = 1"
For Edition 1 the condition is obviously "E1 = 1"
When I tried to use those conditions for prerequisites, they worked perfectly.

Now I've tried to install just Edition 1 on my computer. But the result was, that only the core has been installed but absolutely no Edition.

When I search the log for the features, I find something like this:
MSI (c) (88:20) [10:20:54:925]: Feature: Edition1; Installed: Absent; Request: Null; Action: Null

I hope you can help me with this problem. I'll also send a mail with the aip file.

Best regards,
Tobias
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Merged Module not installed

Hi Tobias,

Most surely the feature is not installed because the condition is not fulfilled. Please note that if those properties are used in the merge module you need to append the merge module's GUID to its name. Like this:

Code: Select all

E1.<guid>
Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
RedDrago
Posts: 33
Joined: Thu Jan 19, 2012 9:23 am

Re: Merged Module not installed

Hello Bogdan,

as you should be able to see in the project I sen't by mail, the properties are NOT used in any of the merged modules and are created in the project itself.
I'am using a custom Action which sets the values to "1" if the corresponding feature should be installed.

This worked perfectly in another project, where I used this approach to determine, wether a chained prerequisite should be installed or not.

In the given project, I first created the features and set their individual conditions. Then I added the Merge Modules to the main project and I associated them with the related feature. I added them by using the "Merge Module Page", I did not add them as a normal file.

But none of these features where installed.

Thanks,
Tobias
RedDrago
Posts: 33
Joined: Thu Jan 19, 2012 9:23 am

Re: Merged Module not installed

After several ettempts it starts to look more like that this is not a problem with the Merge Module.

It's more likely a problem with the features.
Every feature that I added manualy and set the install behavior to based on a condition simply won't be installed.

A part of the log:
MSI (c) (68:60) [11:19:25:241]: Doing action: InstallValidate
Aktion 11:19:25: InstallValidate. Die Installation wird überprüft
Aktion gestartet um 11:19:25: InstallValidate.
MSI (c) (68:60) [11:19:25:374]: Feature: FeatureA; Installed: Absent; Request: Null; Action: Null
MSI (c) (68:60) [11:19:25:413]: Feature: MainFeature; Installed: Absent; Request: Local; Action: Local
MSI (c) (68:60) [11:19:25:441]: Feature: FeatureB; Installed: Absent; Request: Null; Action: Null

Feature A and B are child features of the Main Feature.
The Main Feature is beeing installed by default, but the children are based on a condition. Why won't they be installed, even though the conditions are met? Did I miss something??? :?

Thanks,
Tobias
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Merged Module not installed

Hi Tobias,

The problem is that you are setting the properties used in the install conditions too late, i.e. after the feature states are set using our condition support. This is why we mentioned in our documentation that the condition cannot use properties set on the UI sequence.

The solution for you is to set the features to not be installed by default and on VerifyReadyDlg dialog to use set property events for setting the property ADDLOCAL with
the feature IDs that you want to be installed, using the same conditions from Organization page.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
RedDrago
Posts: 33
Joined: Thu Jan 19, 2012 9:23 am

Re: Merged Module not installed

Thanks a lot, that was the missing point.

Return to “Common Problems”