Windows Service Silent Update: Difference between revisions

Jump to navigation Jump to search
Line 69: Line 69:


*On Firefox (or any other Mozilla application that uses the service) startup, Firefox detects an update is ready to be applied
*On Firefox (or any other Mozilla application that uses the service) startup, Firefox detects an update is ready to be applied
*Firefox checks to see if the service is started; if the service is not started it will start the service.  
*Whether or not the service should be used, Firefox executes updater.exe unelevated.
*Firefox will write out a 'work item' file into the directory being watched with Firefox's session ID, the path of updater.exe, and the command line parameters that are passed to updater.exe
*Firefox shuts itself down.
*updater.exe unelevated checks to see if the service should be used, and if so tries to start the service.  
*updater.exe unelevated will write out a 'work item' file into the directory being watched with the work item details.
*If the service can't be started, is disabled, or does not exist, Firefox will execute updater.exe as it used to without the service.
*If the service can't be started, is disabled, or does not exist, Firefox will execute updater.exe as it used to without the service.
*Firefox shuts itself down.
*If the service was used, updater.exe unelevated waits for a global named event to be set which indicates the update is done.
*Once done updater.exe unelevated will run the callback application and the post update process.


== Applying an update from the service's perspective ==  
== Applying an update from the service's perspective ==  
Confirmed users
394

edits

Navigation menu