> > By now it should be clear what I'm trying to do. A feature dialog is > > being executed *after* CostFinalize and therefore *before* > > ExecuteAction. This dialog determines the set of features to be > > installed. But the actual installation ignores this information. I > > know why, because it needs to be available *before* CostFinalize (see > > description). But in order to make it available *before* the dialog > > chain would need to be moved up in the sequence, something that can't > > happen because of the DM dependency (and possibly others). I think this > pretty clearly sums it up.
Here's something to think about. The feature selection dialog executes after CostFinalize and yet we can configure Directory paths based on user input that occurs after CostFinalize. I have to wonder what you are trying to do (other than run your UI dialogs too early) that might cause problems. I have to assume that you tried it the normal way first and it didn't work as you expected because what you expected did not match the way Windows Installer works. Edwin G. Castro Software Developer - Staff Digital Channels Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail ------------------------------------------------------------------------------ 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
