Upon further research I zeroed in on the primary culprit for the difficulties involving ADDLOCAL. The problem lies with the InstallUISequence itself, particularly the location of CostFinalize in the sequence. Any sort of GUI with multiple dialogs is very likely to require the Directory Manager. Well guess what, DM initialization is not complete until after CostFinalize. Any attempt to re-sequence that causes dialogs to be displayed before CostFinalize will result in Error 2732 (DM not initialized). This effectively locks the display of dialogs between CostFinalize and ExecuteAction. Which in turn means ADDLOCAL cannot be used because of my previous findings. I think it may be time for a brute force solution like including a helper app in the installer.
-----Original Message----- From: Peter Stein [mailto:pst...@instec-corp.com] Sent: Wednesday, July 27, 2011 1:48 PM To: 'WiX-users@lists.sourceforge.net' Subject: [WiX-users] changing features to be installed via ADDLOCAL My installer has a dialog that lets the user choose a feature. Based on that choice ADDLOCAL is modified via a custom action. The problem seems to be that WiX has insufficient granularity with regards to scheduling UI actions. The problem I can't seem to solve is precisely how to schedule this custom action. It seems either one of two things happen with the user's feature selection being ignored in both cases: 1. The action is scheduled too late in which case the original (i.e. before dialog modified) ADDLOCAL is used for the install. 2. The action is scheduled too early in which case the available global value at the time of evaluation is used. I can't seem to hit that spot in the scheduling where a global used to hold the user's feature selection from the dialog can be used via the custom action to update ADDLOCAL. What seems to be needed are elements for the InstallUISequence that have Before and After attributes that can be the IDs of dialogs, i.e. <Custom Action="setADDLOCAL" Before="dialogXYZ"/>. Maybe I'm missing something and ADDLOCAL is not the way to do this, but the recommended alternatives of using conditions in either the features or components don't work because the conditions are evaluated before the feature dialog is run. Suggestions are most welcome. ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
