In article <[EMAIL PROTECTED]>,
Karl Denning <[EMAIL PROTECTED]> writes:
> The application relies on a database, which is unique per installation.
> The database, although is not very large, takes 2-5minutes to build.
> [...]
What I would do is:
1) Have a CA that does the necessary part (I believe you said the
database must exist for the application to function, but it needn't be
populated)
2) At the end of a successful install launch a process that populates
the database in the background.
This assumes that the application and the database population can run
concurrently.
The only rollback concern I see is that on a cancelled or failed
install that causes rollback, the database that was created should be
removed.
--
"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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
