> 1. Can the MSI package be marked in some way so that the > complete MSI > file (under 5 MBs in my case) is cached by Windows Installer? > 2. Can my setup bootstrapper call some MSI API to make Windows > Installer cache the complete package? > 3. Should my setup bootstrapper copy the MSI package to a permanent > location on the local computer and perform the installation from > there? > If so can I prevent the Windows Installer doing it's own caching > since the MSI package will always be available on the > local computer? > > I would obviously prefer option 1 or 2 or any other similar > option that prevents my setup bootstrapper effectively > maintaining an MSI cache of its own. How do you setup > bootstrappers, in general, avoid this issue?
Andrew, I've solved this problem in the bootstrapper. Once the MSI has finished installing, I put a copy of the Msi file in a subfolder of my application, and then call MsiSourceListAddSource to add that directory to the list of source directories for the product. Windows Installer can then find a full copy of the MSI, with no prompts. In my installer I have a RemoveFile and RemoveDirectory element in a component to make sure that the MSI gets deleted on uninstall. Regards, John ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
