You could use three custom actions:
A deferred action that makes a backup copy of the file and then modifies it
(basically what you have now).
A rollback action that would replace the modified file with the backup copy.
A commit action that deletes the backup copy.
--
Stefan Krueger
Microsoft Wi
Kalappa:According to the MSDN MSI help: A rollback custom action must always precede the deferred custom action it rolls back in the action sequence. A rollback custom action should also handle the case where the deferred custom action is interrupted in the middle of execution.
You can do this in
Rollback only works for deferred custom actions. You need to create a rollback
custom action and
sequence it immediately before your other custom action.
Rob
Kalappa Pattar wrote:
> Hi All,
>
>
>
> In my installer, I call utility.exe through VB script.
>
> This utili
Title: Message
Hi All,
In
my installer, I call utility.exe through _vbscript_.
This utility modifies the config file while installing and roll back the changes to config file while un-installing.
Now while installing say the event writing
to the config file
4 matches
Mail list logo