Well, that could happen no matter where you put it. InstallShield puts it in [LocalAppDataFolder]\Downloaded Installations by default but I'm not sure I agree with that. They do this ( as I recall ) so that a setup.exe manifested as Invoker could cache the file for a standard user. Problem (IMO) is that if this then elevates and gets installed for all-users it becomes a managed installation and that user who cached it could then tamper with the MSI and do a repair to inject untrusted code into the installer. Remote, but possible.
The used to cache it in [WindowsFolder]Downloaded Installations but that required Admin privs. I think personally I've used [CommonAppDataFolder]Downloaded Installations before. When I need a setup.exe I typically manifest it as requireAdmin so that each of my prereqs don't require elevation. I've read that this isn't the best practice but I really don't like the alternatives. I've also written some code that's used during major upgrades to delete the previous versions of the MSI that way they don't pile up into something huge. I usually just leave the final MSI behind on uninstall as the size is typically quite small. I'd look at WiX 3.6 and see what approaches Rob is taking with Burn. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me ----- Original Message ---- From: Quinton Tormanen <quint...@deltamotion.com> To: General discussion for Windows Installer XML toolset. <wix-users@lists.sourceforge.net> Sent: Tue, November 30, 2010 4:10:52 PM Subject: Re: [WiX-users] Saving the MSI file Where do you cache it to? Everywhere else I thought of won't get cleaned up and/or might get erased prematurely (e.g. TMP folder). --Quinton -----Original Message----- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Tuesday, November 30, 2010 2:03 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Saving the MSI file I usually just let my bootstrapper handle the caching for me before invoking the MSI. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me ----- Original Message ---- From: Quinton Tormanen <quint...@deltamotion.com> To: General discussion for Windows Installer XML toolset. <wix-users@lists.sourceforge.net> Sent: Tue, November 30, 2010 3:46:28 PM Subject: [WiX-users] Saving the MSI file This issue must have discussed dozens of times, but I couldn't find anything. Quite simply, I want to ensure that our full MSI file is available for repairs later (there's a issue currently out of our control that makes this necessary related to the DifxApp toolkit). Our MSI is only 12MB and the benefit of having it available seems to outweigh this teensy amount of storage space. Here is an approach that I was going to look into but, wanted to hear if I'm all wet before I go too far with it: 1. Copy the MSI being used for the install from the source given by the DATABASE public property to a file in my install file. This assumes I can copy the file while it is open. 2. Ensure that the DATABASE public property is updated to hold the location I copied it to, so that it can get put into the ARP for use by later installs. 3. Ensure that this MSI copy is deleted on an uninstall. 4. See if I can include the MSI size in the file size cost estimate. Does this approach seem at all viable? Is there a better way to do it? What do I need to watch out for? Should I try to get the local copy in the LocalPackage or InstallSource entries in the ARP? --Quinton ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
