In article <[EMAIL PROTECTED]>,
Karl Denning <[EMAIL PROTECTED]> writes:
> That's roughly what we have.
Except you're doing the CPU hungry bit as part of the install
transaction. It doesn't need to be there. Trying to put it there is
giving you the headache of trying to figure out how to display a
temporary UI that the user can cancel.
By moving it out of the install transaction and into a utility launched
on a successful install, you can display a UI that allows the impatient
user to cancel it. To the user's perspective, its still running "at
install time", but you're not messing with windows installer in order to
get what you want.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
