jfaiga
Posts: 25
Joined: Wed Sep 13, 2006 8:21 am

Independent CAB files in Update Configuration Projects

It seems as though cab files are not supported in the "Update Configuration Project"...

Using Advanced Installer 4.5, I have set it to make "Multiple Volumes" of CAB files (which are external to the MSI database).

This installs fine when the files are on the local machine, however I'm having problems with the auto update feature downloading the cab files.

If I dont mention the .cab files in the ".aiu" file on the website, then only the .msi is listed (with only its size mentioned).

When doing an "add update" in a "Update Configuration Project", the only supported files are "*.msi,*.msp,*.exe". *.cab is not mentioned.

If I manually add the .cab files in the ".aiu" file on the website (as a dependancy of the msi), then the cab files is opened as a separate "installation" instead of being part of the msi installation.

So my question is when is there planned support for cab files in the "Update Configuration Project" ? Is there a manual workaround available?
jfaiga
Posts: 25
Joined: Wed Sep 13, 2006 8:21 am

Similarly, it looks like patches must currently be to msi's that contain full cab files.
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi,

The updater does not support to have multiple files as an update. But please tell me why you need to create multiple cab files and distribute them as an update?
If I manually add the .cab files in the ".aiu" file on the website (as a dependancy of the msi), then the cab files is opened as a separate "installation" instead of being part of the msi installation.
The dependency feature referees to this: If an update A needs (depends) an older update B prior to run then add this older update B as dependency for the update A.

Also for more details about how to use the updater please see:
http://www.advancedinstaller.com/user-g ... -page.html

Regards,
Gigi
________________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
jfaiga
Posts: 25
Joined: Wed Sep 13, 2006 8:21 am

Putting the cab file into our msi gives a large msi.

This msi needs to be installed at some clients that have external internet access, and some that do not have external internet access.

For the ones that do not have external internet access, it will be easier for us to distribute to them if the distribution sets are limited to a particular size.

Therefore I'm looking into using cab files for the auto update so that we can have the same distribution package for both clients that have external internet access, and those that dont.

However the functionality requested is for cab files support in both auto updates and patches.

If this feature is not available, it is not critical for us, as we can compress the msi into multiple volumes ourselves. However that is not the ideal solution.
bkavanaugh
Posts: 10
Joined: Tue Jul 17, 2007 4:37 pm

CAB files and Updates

Has this changed any with the newer versions? We have a similar situation as the original poster: there is a feature that only a handful of external users will use, so when we do updates, there is no reason for everyone else to download it.

The help file seems to imply this is possible (Media Tab): "This is useful when installing the MSI from an URL location as only the CABS corresponding to the features selected for installation will be downloaded."

It does seem to work that way on the initial install. However, when we issue an update, it'll complain about the cab files missing on the local machine. Is there some other way to accomplish this, or any plans to implement it?
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,

The solution for what you need is to use an EXE bootstrapper for your update. Here are the steps:
- in the "Media" page you go to the "Bootstrapper" tab and check the "Create EXE setup file" option
- in the "Package" section you select the "Retrieve from online location" option and you set the URL where the MSI and the CAB files will be placed
- you build the project, copy the resulted EXE file and place the generated MSI and CAB files in the URL you specified in the previous step
- in the Updates Configuration Project add the EXE as an update

When the updater will run, it will find the EXE and it will launch it. After it is launched, the EXE downloads only the necessary CAB files and runs the installation.

You can read more about the "Media" page here:
http://www.advancedinstaller.com/user-guide/media.html
http://www.advancedinstaller.com/user-g ... apper.html

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
bkavanaugh
Posts: 10
Joined: Tue Jul 17, 2007 4:37 pm

Okay, I had always had it pointing at the msi, not the exe. How do you update the prerequisites, though? Doesn't the bootstrapper need the ini file?
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Hi,
How do you update the prerequisites, though? Doesn't the bootstrapper need the ini file?
I'm not sure why you need to update the prerequisites when performing an update. Note that if your application changes dramatically and needs other prerequisites you should release a new independent installation package (you should not use the Updater).

However, in order to include the INI file in the EXE you can follow these steps:
- go to the "Media" page, select the "Bootstrapper" tab and set the "Include install files in EXE"
- in the "Media" tab set the "One CAB archive per feature" option
- in the "Bootstrapper" tab set the URL which will hold the CAB files and the MSI

Note that the EXE will contain the INI file and the prerequisites and the URL will hold the CAB files and the MSI. Also, this installation package will work only with the CAB files and the MSI in the online location (it will not work if all files are in the same location).

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”