Microsoft Updater Application Block 1.5.1 Configuration Design

Microsoft Updater Application Block configuration design



Translator: Tony Qu

The configuration information of the application installer has three sources:

1. application configuration file of the application installer-This file contains information about the polling interval, log location, the download server to be used, and the validators, the specific information of each application to be included during the upgrade process. For each application, the file contains the client settings (such as the location of the client configuration file) and server settings (such as the location of the manifest file required for upgrading a specific application ).

2. Client configuration files-in fact, these files are application configuration files associated with the Application Loader, which are prepared for each application upgrade. This file contains information necessary to identify the currently installed version and the location of the executable file to be loaded.

3. Manifest file-every time a specific application is published on the server, a manifest file must be created for updates. This file contains the version to be upgraded, the file list in the upgraded version, and information about the post-processor that needs to be executed after the update. This file also contains each file and its own authentication signature, which allows the application installer to verify and upgrade, and can prevent unauthorized upgrades or interception attacks.

In the Application installer, each file is deserialized into a corresponding object. The application installer configuration file is mapped to the UpdaterConfiguration class. Each client configuration file is mapped to the ClientApplicationInfo class, and each manifest file is mapped to the ServerApplicationInfo class. As shown in:


This section contains the following topics:

Application installer Configuration Design

Client Configuration Design

Manifest file Design