The problem with is rollback. If we have one deferred custom action for
all drivers, then we need to know what action failed, so we have to
write somewhere what actions we have done and what to do to rollback
each of them.
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Frida
Rob, Blair thank you very much for your explanation!
I haven't known that the immediate custom action can schedule the same
deferred custom
action multiple times. I will try it now. If I'll have some problems
with it I will ask for help.
Regards,
Maks
-Original Message-
From: Blair [mailto
As I understand in this approach there will be one immediate ca (that
will marshal the data to the deferred) and only one deferred custom
action that will configure all drivers.
If there will be a custom actions for each action to driver, I will have
to describe them all in my wixlib.
The problem
I work on WiX-based installer for large product, we need to install 16
drivers (of 3 different types, so there is 3 installation patterns).
Difx library is not flexible enough, so we have our own tool to install
drivers. For each driver necessary to run this tool about 3 times (for
example: remove
4 matches
Mail list logo
