I deploy an unversioned file (with a CompanionFile setting) and modify the file during the install based on GUI entries. The repair case does not present the whole GUI, just the maintenance dialog, so during a repair, the file gets redeployed but the GUI entries are not available to re-modify it. I want to suppress the redeployment of that modified file during repairs.
The user will not set REINSTALL on the command line, and 'light' warns me not to put REINSTALL in the property table. I tried the 'transitive' setting, but that didn't help (the file is always redeployed in the repair case). I cannot figure out how to avoid redeploying that file during repairs. I could write CAs to save the file and restore it after redeployment when repairing, but that seems hokey. Is there, or is there not, a standard way to NOT redeploy a file (or component or feature) during repairs, when the user double-clicks the MSI file (not command line) ? I see a related posts, but I'm just not seeing a straight answer. Thanks, Gary ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
