Re: [WiX-users] How do setup bootstrappers avoid prompts for media when changing or repairing an existing installation
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? Best regards, Andrew -- Andrew Lee Solarflare Communications mailto:a...@solarflare.com http://www.solarflare.com/ -- 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 -- 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
Re: [WiX-users] How do setup bootstrappers avoid prompts for media when changing or repairing an existing installation
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
[WiX-users] How do setup bootstrappers avoid prompts for media when changing or repairing an existing installation
I am using a (custom written) setup bootstrapper with an embedded MSI package, the bootstrapper extracts the MSI package to a temporary directory, performs the installation and then deletes the temporary directory. When later via Add/Remove Programs I try to add extra features or sometimes during a repair the Windows Installer prompts for the media with The feature you are trying to use is on a network resource that is unavailable. Unfortnuately as the MSI package is embedded inside my setup bootstrapper I can't provide a valid path to Windows Installer at this point. One potential solution is to mark the package so that Add/Remove Programs only offers a remove/uninstall option, but if possible I'd prefer to keep the change/modify and repair options. In trying to resolve this I have subsequently read that Windows Installer caches MSI packages with any embedded files and cabinets stripped out. 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? Best regards, Andrew -- Andrew Lee Solarflare Communications mailto:a...@solarflare.com http://www.solarflare.com/ -- 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
Re: [WiX-users] How do setup bootstrappers avoid prompts for media when changing or repairing an existing installation
All MSI packages are cached my Windows. See: C:\WINDOWS\Installer -Original Message- From: Andrew Lee [mailto:a...@solarflare.com] Sent: January 22, 2009 07:39 To: WiX-users@lists.sourceforge.net Subject: [WiX-users] How do setup bootstrappers avoid prompts for media when changing or repairing an existing installation I am using a (custom written) setup bootstrapper with an embedded MSI package, the bootstrapper extracts the MSI package to a temporary directory, performs the installation and then deletes the temporary directory. When later via Add/Remove Programs I try to add extra features or sometimes during a repair the Windows Installer prompts for the media with The feature you are trying to use is on a network resource that is unavailable. Unfortnuately as the MSI package is embedded inside my setup bootstrapper I can't provide a valid path to Windows Installer at this point. One potential solution is to mark the package so that Add/Remove Programs only offers a remove/uninstall option, but if possible I'd prefer to keep the change/modify and repair options. In trying to resolve this I have subsequently read that Windows Installer caches MSI packages with any embedded files and cabinets stripped out. 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? Best regards, Andrew -- Andrew Lee Solarflare Communications mailto:a...@solarflare.com http://www.solarflare.com/ -- 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 -- 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
Re: [WiX-users] How do setup bootstrappers avoid prompts for media when changing or repairing an existing installation
Eric Teutsch wrote: All MSI packages are cached my Windows. See: C:\WINDOWS\Installer Yes I realise that, but the cached package has all embedded files and cabinets stripped out to save space. So when adding a feature to an existing installation, the cached package does not include the needed files and the installer prompts for the path to the original media. I want to be able to avoid such prompts. Best regards, Andrew -- Andrew Lee Solarflare Communications mailto:a...@solarflare.com Block 2, Second floor, Westbrook Centre tel:+44-1223-518040 x5507 Milton Road, Cambridge, CB4 1YG, UK fax:+44-1223-464225 http://www.solarflare.com/ -- 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
Re: [WiX-users] How do setup bootstrappers avoid prompts for media when changing or repairing an existing installation
I believe products like Microsoft Office extract the MSI to a folder and leave it on your system to allow for changes. Neil Neil Sleightholm X2 Systems Limited n...@x2systems.com mailto:n...@x2systems.com From: Andrew Lee [mailto:a...@solarflare.com] Sent: Thu 22/01/2009 13:06 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How do setup bootstrappers avoid prompts for media when changing or repairing an existing installation Eric Teutsch wrote: All MSI packages are cached my Windows. See: C:\WINDOWS\Installer Yes I realise that, but the cached package has all embedded files and cabinets stripped out to save space. So when adding a feature to an existing installation, the cached package does not include the needed files and the installer prompts for the path to the original media. I want to be able to avoid such prompts. Best regards, Andrew -- Andrew Lee Solarflare Communications mailto:a...@solarflare.com Block 2, Second floor, Westbrook Centre tel:+44-1223-518040 x5507 Milton Road, Cambridge, CB4 1YG, UK fax:+44-1223-464225 http://www.solarflare.com/ -- 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 -- 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
Re: [WiX-users] How do setup bootstrappers avoid prompts for media when changing or repairing an existing installation
Andrew Lee wrote: 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? No. 2. Can my setup bootstrapper call some MSI API to make Windows Installer cache the complete package? No. 3. Should my setup bootstrapper copy the MSI package to a permanent location on the local computer and perform the installation from there? Yes. That's what other apps like Office do. 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? No. As they're stripped, they're usually small. The exception is if you have large files in the Binary table, for example, because that data isn't stripped out. -- sig://boB http://joyofsetup.com/ -- 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
