Merge Modules vs Chained MSI - 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!

Dashut
Posts: 142
Joined: Tue May 04, 2010 4:41 pm

Merge Modules vs Chained MSI

Using 7.6.1: I basically want to have a "base"/"master"/"main" MSI that installs 3 Services (three different components/merge modules/chained msi's).
We are currently trying to understand:
Is it best to have 3 MSI's for each Service that we want to install, and then the MAIN MSI install them as "chained msi"?
Or is it best to have 3 Merge Modules for each Service (3 executables which are independent Services) and then have the MAIN MSI install them?

What I see is: for MSN Merge Modules, I don't have the "Services" tab which exists for MSI projects. This makes me believe that I might have to use "chained msi"s if I want each Component to register itself (because you already give this option in the installer for MSI's but NOT for Merge Modules).

Also: how can I add the MSN or Chained MSI's as components in the "Special Dialogs/CustomizeDlg/SetupTypeDlg" so that a User can choose "Custom" (rather then "typical" or "Complete") and then choose which component he wants to install?
Is this possible only with MSI's? Only with MSN? or both?

Thanks for all your help, Dashut.
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Merge Modules vs Chained MSI

Hello,

Why not organize your application into features? That's the correct way to split your product into installable modules.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
Dashut
Posts: 142
Joined: Tue May 04, 2010 4:41 pm

Re: Merge Modules vs Chained MSI

Yes, but when you organize the application as features, it just stores/saves/copies the files to the destination folder: it does NOT install them!
As I understand, when I use MSN or Chained MSIs: it installs them.
Using MSI's for each service, gives us the opportunity to have every developer create his OWN MergeModule(MSN) or MSI.
I don't think that I can run Chained MSI's or MergeModules with "Features". Correct?

Dashut.
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Merge Modules vs Chained MSI

Hi Dashut,

What I mean is the developers should not create each his own msi. Their content should be placed in the main .aip directly under the corresponding feature.

MSMs and Chained MSIs are not for this purpose. They are intended to provide third-party functionality to your application in form of runtimes and other resources for your application.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
Dashut
Posts: 142
Joined: Tue May 04, 2010 4:41 pm

Re: Merge Modules vs Chained MSI

I just checked, and it's possible to have "Chained MSI's" selected as "Feature". So this can be what we're looking for.
I looked at: http://www.advancedinstaller.com/user-g ... -page.html so when I added a MSI (in "Chained Packaged"), I then go to the "install" group and press "..." in the "condition". I then press the wizard option that opens: "Welcome to the New Condition Wizard", and I select the bottom choice which is: "feature" and then in the next window in "this feature" I choose my feature.

Please correct me if I'm wrong here.
Thanks, Dashut.
Dashut
Posts: 142
Joined: Tue May 04, 2010 4:41 pm

Re: Merge Modules vs Chained MSI

I just created a "main" MSI with two Chained MSI's and connected them to the "Features".
So the Features I have in the "Custom Setup" window are:
1. "MainFeature" (which is the default that AdvancedInstaller creates).
2. "Chain1" - was created by me for the first Chained MSI (some simple msi I created before creating the MAIN msi).
3. "Chain2" - another MSI connected to this feature.

Two problems:
1. When selecting with the mouse "MainFeature" I get on the right side: "This feature requires 344kb on your hard drive." - which is true, because I added some file there for my "main msi". BUT!!! When I choose (with the mouse) either Feature: "Chain1" or "Chain2" I get: "This feature requires 0kb on your hard drive." although the both MSI's are about 1mb... so this looks like a bug to me.

2. When choosing either of the "Chain1" or "Chain2" Features, I have the following list to choose from:
* Will be installed on local hard drive
* Entire feature will be installed on local hard drive
---
* Will be installed to run from network
* Entire feature will be installed to run from network
---
* Feature will be installed when required
---
* Entire feature will be unavailable

I want to have the User choose _either_: "Will be installed on local hard drive" _OR_ : "Entire feature will be unavailable" and none of the rest!
How can I do that?

Dashut.
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Merge Modules vs Chained MSI

Hello,

Yes, this might be something you want, however it is important to note chained packages only work with Windows Installer 4.5 and later. It is best if you set Windows Installer 4.5 as a prerequisite to ensure your installer works properly even on systems which don't have 4.5 preinstalled.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
Dashut
Posts: 142
Joined: Tue May 04, 2010 4:41 pm

Re: Merge Modules vs Chained MSI

Okay, I'll have Windows Installer 4.5 as a prerequisite. Thank you for reminding me.

About my two questions (asked in my previous reply):
1. was about incorrect calculation of the "feature" (for details: read in my previous reply).
2. and my second question was about how to reduce feature options (also please read in my previous reply).

Waiting for your help on this one, Dashut.
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Merge Modules vs Chained MSI

Hello,

How exactly are you connecting the chained MSIs to features? It might explain why you are getting 0kb on the reported size.
The "run from network" options appear for features that are empty, which might be your case (most likely related to the 0kb issue too). To avoid this place a dummy registry value under that feature.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
Dashut
Posts: 142
Joined: Tue May 04, 2010 4:41 pm

Re: Merge Modules vs Chained MSI

How I am connecting to chained MSI to features:
1. Under "Deployment" -> "Organization" I right click on "Product" and select "New Feature". I name it "Chained1" (important! I will connect to this feature name at the end).
2. Under "Requirements" -> "Chained Packages" I add my MSI called: "chained1.msi".
3. Then in the left side "Options" there's the "Install" group which has "Condition:" and "...". I press the "..." button, and then the "Edit Condition" window appears.
4. I then press the wizard button, and a new window "New Condition Wizard" appears.
5. I press "next" and then I have to choose from 5 options. The option on the bottom is: "Feature", and then I press "next".
6. Then a new window I have the "The feature" and "...". So I press the "..." button and choose the feature I created in step 1: "Chained1".

and that's how I "connect" ChainedMSI with Feature.
Now the question is: why I get 0kb size.

Waiting, Dashut.
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Merge Modules vs Chained MSI

Hi Dashut,

The reason you are getting 0kb is the following:
- you are creating an empty feature on the Organization page. It does not have any components under it whatsoever.
- you are conditioning the installation of a chained package depending on whether that feature will be installed or not. However, that does not mean the chained package itself belongs to that feature. You are simply conditioning it to install IF that feature installs. The feature itself is still empty, thus the 0kb reported size and thus the install from network menu item.

I am afraid there is no way Windows Installer will be able to report the size of the installed chained package(s).

What you can do is create a new component containing some dummy resource (perhaps a registry value?) under that empty feature (e.g. Chained1), select the component and select "Reserve additional disk space for this component". Set it to the size of the chained package. This way at least it wouldn't report 0kb.

I hope this helps.

Regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/
Dashut
Posts: 142
Joined: Tue May 04, 2010 4:41 pm

Re: Merge Modules vs Chained MSI

"Reserve additional disk space for this component" - will most probably work, but then the MSI size (of the Chained) can change, and I don't want to revisit this part of the Installer every time...
Do you think you can somehow have the "Reserve additional disk space for this component" connected to the MSI?
I mean, I now understand the problem as you explain it, however, is there a way for you to provide some "automatic" calculation, so that I will not have to calculate the MSI size every time? (some checkbox...).

And the other question is: Can I have only TWO options presented to the User? :
"Will be installed on local hard drive" or "Entire feature will be unavailable" and that's it! so basically: it's like a checkbox (because if I use checkboxes, I have to create an EXE installation - but I want MSI...).
Dashut.
GabrielBarbu
Posts: 2146
Joined: Thu Jul 09, 2009 11:24 am
Contact: Website

Re: Merge Modules vs Chained MSI

Hello Dashut,

Unfortunately there is no way but to maintain that value.
You could try searching for a free command line tool that can edit XML files and set up your build system to use it to edit the aip and maintain that value.

Regarding your second question, there is no way to edit that menu since this is controlled entirely by Windows Installer.

I hope this helps.

Best regards,
Gabriel
Gabriel Barbu
Advanced Installer Team
http://www.advancedinstaller.com/

Return to “Common Problems”