FileCost with Chained MSI - Advanced Installer Community
b.biene
Posts: 66
Joined: Thu Nov 08, 2012 4:21 pm

FileCost with Chained MSI

Hello,

i have alot Chained-MSI packages in my installer. The calculated FileCost showing the requiered Disk-Space seems not to include the space-requirements from the chained packeges.
How can i fix this?
b.biene
Posts: 66
Joined: Thu Nov 08, 2012 4:21 pm

Re: FileCost with Chained MSI

Any sugestions?
b.biene
Posts: 66
Joined: Thu Nov 08, 2012 4:21 pm

Re: FileCost with Chained MSI

Is there mayby a way to configure the filecost manually?
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: FileCost with Chained MSI

Hi,

I apologize for the delayed reply.

Indeed, the space required by the chained packages is not calculated in the space required of the main package. I'm afraid that this is a limitation that we cannot workaround.

In order to manually add the size of the chained MSI to the required disk space, you can go in the "Organization" page, choose a component and use the "Reserve additional disk space for this component" option for it, then set for it the same condition that is used for the chained package.

In this case, that component will be installed only when the chained package is installed and it will reserve the disk space that you written for it.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
b.biene
Posts: 66
Joined: Thu Nov 08, 2012 4:21 pm

Re: FileCost with Chained MSI

Hi,

thanks for that. I did add the space of the chained packeges and the prerequisites to the additional space of the features. But now the total space is assigned in the programlist (install / uninstall) to my application.
But the prerequisites has there own entry (with space). I know i can fix this with the Product-Details Custom disk size. But if i enter a fixed value, this would not change if i deselct a feature. The other downside is that if i add or remove files to my project i have to manually recalculate the disk space.
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: FileCost with Chained MSI

Hi,

In order to avoid this behavior you can follow the steps below:
- move the components that have the "Reserve additional disk space for this component" option set for them, to their own features
- set the "Not Displayed" option for those features
- go in the "Dialogs" page and click on the "Install" button from the "VerifyReadyDlg" dialog
- add an "Uninstall one or more features" published event for each of these features, so those components will not be installed
- build and run the project

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”