2 replies to this topic

[ricklin]

Hi,

I am using the Basic MSi project in Installshield 10.5 Pro. I am trying to use the "self-healing" feature (aka feature on demand) when installing from an MSI install program. During self-healing, the original MSI install will NOT be availble to the PC. However, self-healing requires the MSI file to be available or to be cached in Windows Downloaded Installations directory. As far as I know, Installshield does not have an option to cache the MSI file for an MSI install, only the setup.exe install. Does anyone know how I can force the MSI file to be cached and used when self-healing occurs? Thanks.


Rick

[Glytzhkof]

The general idea of self healing is to provide installation on demand using and administrative installation placed on a network share. If you install from a network share windows installer will be able to pull the files from this location during self repair.

I don't know of any robust way to cache the whole MSI installer on the system without a setup.exe wrapper.

[Stefan Krueger]

The msi file minus any embedded CABs will automatically be cached in the Installer directory.
However for a repair Windows Installer needs access to the application files, either uncompressed (typically on a CD), compressed in one or more CAB files, or an msi file with embedded CABs.
The easiest way is the use of a setup.exe that will extract and permanently store these files on the user's hard disk. You may be able to use a custom action to copy the setup files, and in addition change the source location list, but I've never tried this.