Re: [WiX-users] Why is WiX UI executed after CostFinalize?

So I assume that the AddLocal and Remove events wouldn't function if I ran the UI earlier? That certainly isn't documented anywhere that I can find. It is certainly the case that ADDLOCAL and REMOVE can be set before CostFinalize for example on the command line so I am surprised. The nearest to a

[WiX-users] Why is WiX UI executed after CostFinalize?

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