I have suffered form the standard problem that many people on this mailing list hit where conditions on features apparently don't work because the UI is executed after the CostFinalize action when these are applied.
Why is the UI run after Cost Finalize rather than before it? If the UI were run earlier then Feature conditions would work in the obvious manner but I assume other problems would occur. Does anyone know what those problems are likely to be? Are they less troublesome than the problems caused by the existing order of execution? Thanks in advance -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Why-is-WiX-UI-executed-after-CostFinalize-tp6047911p6047911.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
