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
