Re: [WiX-users] Working around the CostingComplete bug

2010-12-02 Thread Rob Hamflett
So I tried removing the 'wait for costing to complete' dialog from one of our installers to test it out. This morning I have a crash report that msiexec crashed in CostAllComponentsWorkerThread. Google, Bing and MSDN return zero results when I search for it. Does anyone know anything about

Re: [WiX-users] Working around the CostingComplete bug

2010-11-29 Thread Bob Arnson
On 26-Nov-10 06:31, Rob Hamflett wrote: > Slight typo. This was meant to say "It would be nice to know what I can > expect to happen if costing > *hasn't* completed yet" AFAICT, costing completed; only the property wasn't updated. -- sig://boB http://joyofsetup.com/ -

Re: [WiX-users] Working around the CostingComplete bug

2010-11-26 Thread Rob Hamflett
>It would be nice to know what I can expect to happen if costing has completed >yet. Slight typo. This was meant to say "It would be nice to know what I can expect to happen if costing *hasn't* completed yet" Rob On 25/11/2010 16:41, Rob Hamflett wrote: > It would be nice to know what I ca

Re: [WiX-users] Working around the CostingComplete bug

2010-11-25 Thread Rob Hamflett
I'm not using the WiX UI, so I don't think just upgrading to 3.5 would fix things. However the change appears to be the same, which is to just bypass the 'please wait' dialog, so I guess I'll just go along with that. It would be nice to know what I can expect to happen if costing has complete

Re: [WiX-users] Working around the CostingComplete bug

2010-11-25 Thread Neil Sleightholm
Bob has blogged about this here: http://www.joyofsetup.com/2010/10/09/experimental-results-part-ii/ which may help. The simplest fix is to upgrade to WiX 3.5. Neil Neil Sleightholm X2 Systems Limited n...@x2systems.com