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
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/
-
>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
2systems.com>
>
>
>
>
> From: Rob Hamflett [mailto:r...@snsys.com]
> Sent: Thu 25/11/2010 09:40
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Working around the CostingComplete bug
>
>
>
> To work around the bug whe
ms.com <mailto:n...@x2systems.com>
From: Rob Hamflett [mailto:r...@snsys.com]
Sent: Thu 25/11/2010 09:40
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Working around the CostingComplete bug
To work around the bug where in Windows Install
To work around the bug where in Windows Installer 4.5 where CostingComplete
does not get set, is it
OK to just remove the SpawnWaitDialog call from the Welcome dialog's 'Next'
button? I've seen a
number of suggestions to do this as a fix, including a comment on a changeset
for WiX. Specifica
6 matches
Mail list logo
