I was looking for some help with the following: I've built the installer to request a value from the user before doing initial installation. I then store this value in a registry location. If the user then does a 'Change' installation, I allow them to change the value (it's a directory path), and attempt to re-store this value in the registry. I used the 'put a registry setting in its own feature, then reinstall the feature' trick to try to get the value into the registry. I'm running into some issues, though, and was wondering if somebody had some insight.
Issue #1: Obviously, I don't want to do the reinstall of the feature when REMOVE="ALL" (the reinstall of the feature negates the uninstall.) However, the 'ALL' value isn't available until after the InstallValidate step. But it appears from looking at the verbose msiexec install log that the action to take on the feature is determined at the beginning of the InstallValidate step. So what sort of condition can I write to test REMOVE before InstallValidate? Issue #2: I found that REMOVE will be set to a list of all features early on using the UI (this is then converted to "ALL" during InstallValidate), so thought I'd try testing if the hidden feature I wanted to possibly reinstall was included. That worked, except when you try to uninstall via the Programs dialog, as that doesn't run the installer UI, so the value of REMOVE isn't available, so the reinstall happens, causing the uninstall to fail. Again, any idea of a condition to make this work? Issue #3: I tried an experiment where I forced REINSTALL to the feature I wanted to reinstall, before InstallValidate, but the verbose log showed during InstallValidate that the feature was already installed and no action was planned. Can somebody tell me when REINSTALL is actually checked to decide if a feature should or should not be reinstalled? Apparently, from my test, setting it before InstallValidate is the wrong time. Any clues, or pointers to things to look at (other than "check the verbose log", because I'm already doing that) would be greatly appreciated! Dave ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
