Windows Installer XML toolset.
Subject: Re: [WiX-users] Adding buttons to the ProgressDlg
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
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
That's roughly what we have.
The algorithm that generates the records is CPU hungry, which is one reason
to offload it to the installer - get as many records generated when user
doesn't care so much about performance issues.
We have a load of other optimization tricks in place, but this one gives
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
lto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2008 11:54
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding buttons to the ProgressDlg
I'm on the verge of trying that.
async + wait for return code looks like the type I should use.
I've been digging around MSD
t
Subject: Re: [WiX-users] Adding buttons to the ProgressDlg
Sorry - I was trying to reduce the task to a minimal sentence because the
big
picture is fairly complicated, and I think will turn off most people.
Here goes
The application relies on a database, which is unique per installation.
The
Async CustomAction?
-Original Message-
From: Karl Denning [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 19, 2008 10:29
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding buttons to the ProgressDlg
Sorry - I was trying to reduce the task to a minimal sentence
Sorry - I was trying to reduce the task to a minimal sentence because the big
picture is fairly complicated, and I think will turn off most people.
Here goes
The application relies on a database, which is unique per installation.
The database, although is not very large, takes 2-5minutes to
In article <[EMAIL PROTECTED]>,
Karl Denning <[EMAIL PROTECTED]> writes:
> Is it possible to add a hidden control (in my case a button) to the
> ProgressDlg, which is hidden until a specific DEFERRED custom action is
> executed?
What is it you really want to achieve with this mechanism?
An
9 matches
Mail list logo
