Hello Edhy,

Currently the best method to use to deploy the Update Service during an update is to create a simple MSI that installs the service using the merge module that ships with AppLife Update. Using the merge module will ensure proper reference counting on the installed service.

This MSI can be executed during an update using the Execute MSI action. Then, use the Registry update actions to add the necessary registery entries for your application to use the update service. You will need to register the full path of your host executable. You can access the physical path to your exe on the deployed client by using the Set Shared Property action.  With this action, you can select the ApplicationDirectory and assign that to a shared property which you can use in the registry actions.

It is important to recognize that your users must have adminstrative privileges when this update is applied, or the update will fail. Only after the service is present and your application registered, will limited users be able to apply updates that require privileges.

Hello Edhy,

On the update controller, set the ElevationType property to AppLifeWindowsService.

After that, your updates will launch using the service.  When using the service, your update actions cannot interact with the user.  If you are launching any other processes using the Command Line action, MSI action, Dynamic Code Action, or custom actions, they must operate silently.

Other than that, the update process will be identical to a non-serviced update.

Has anyone done this with Visual Studio? 'Currently the best method to use to deploy the Update Service during an update is to create a simple MSI that installs the service using the merge module that ships with AppLife Update.'