Adobe AIR 3 introduces features that provide developers a consistent and flexible development environment for the delivery of out-of-browser applications across.
Users can install or update an AIR application by double-clicking an AIR file on their computer or from the browser (using the seamless install feature). The Adobe® AIR® installer application manages the installation, alerting the user if they are updating an already existing application. However, you can also have an installed application update itself to a new version, using the Updater class.
(An installed application may detect that a new version is available to be downloaded and installed.) The Updater class includes an update() method that lets you point to an AIR file on the user’s computer and update to that version. Your application must be packaged as an AIR file in order to use the Updater class. Applications packaged as a native executable or package should use the update facilities provided by the native platform.
Both the application ID and the publisher ID of an update AIR file must match the application to be updated. The publisher ID is derived from the signing certificate. Both the update and the application to be updated must be signed with the same certificate. For AIR 1.5.3 or later, the application descriptor file includes a element. You must use this element if there are versions of your application developed using AIR 1.5.2 or earlier. For more information, see. As of AIR 1.1 and later, you can migrate an application to use a new code-signing certificate.
Migrating an application to use a new signature involves signing the update AIR file with both the new and the original certificates. Certificate migration is a one-way process.