[wix-users] (no subject)
osito at live.com
Tue Feb 2 22:12:24 PST 2016
Depends on the value of your MajorUpgrade/@Schedule attribute. I had an answer ready, but you wrote “halt my freshly-started background service”.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
From: Brannon King<mailto:Brannon.King at asirobots.com>
Sent: Monday, February 1, 2016 4:04 PM
To: wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>
Subject: [wix-users] (no subject)
As part of one of my installers, I need to start a background process when it is done copying files. When updating I need to stop the process and restart it again after the files have been updated. When uninstalling, I need to stop the process before the files are removed. Using the sequence below, it appears that when I’m updating to a newer build, the “Stop” call happens after the file copy is attempted. It fails to overwrite the files that were executing. Also, I know that the previous bundle is removed with a -quiet call to the same installer, and I never want that to halt my freshly-started background service. What is the right Before/After and conditions for my scenario?
<Custom Action="StartBackgroundService" Before="InstallFinalize">NOT (REMOVE ~= "ALL") AND BUNDLESAYSSTARTBACKGROUNDSERVICE</Custom>
<Custom Action="StopBackgroundService" After="InstallInitialize">Installed OR (REMOVE ~= "ALL")</Custom>
This message contains confidential information and is intended only for the recipient. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately if you have received this e-mail by mistake and delete this e-mail from your system. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
More information about the wix-users