http://msdn.microsoft.com/en-us/library/aa368048(v=vs.85).aspx
CostFinalize must be run before UI is displayed to allow Features to be selected or Directories to be changed, which most installer UIs allow users to do. If you are changing properties that affect component/feature conditioning in your UI, you can run CostFinalize again to have the installation states reevaluated. You just need to execute the CostFinalize action from a DoAction control event after the appropriate property values have been set. -Mike -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Why-is-WiX-UI-executed-after-CostFinalize-tp6047911p6049379.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
