License Management
AppLife™ Update is licensed per builder. A builder is defined as a person or process that interacts to build and publish updates using the AppLife™ Update tools.
The Update Controller assembly and features can be distributed royalty free with your applications, so long as the updates being created for the application are created by a licensed user.
Single Builder License
A single builder license allows one specific user to build and publish updates. The user can build and publish using any number of computers, so long as the logged in user holds a valid license.
Limited Licensing
Many applications do not require the full capabilities of AppLife™ Update. For these applications, we offer a free limited license. A limited license grants access to the robust application updating framework within AppLife™ Update with the option to upgrade at any time. The full features of AppLife™ Update can be added at any time by simply converting your limited license to a full license. Your full license can be applied to the AppLife Update software you are already using.
Feature Matrix
|
General Features |
Full |
Limited |
|
Complete, built in update process user interface |
|
|
|
Comprehensive API to control the update process |
|
|
|
Discrete API methods to check for updates |
|
|
|
Discrete API methods for downloading updates |
|
|
|
Integrate update publishing directly into automated build processes |
|
|
|
Localized update process (en, de, es, fr, it, ja, zh-CHT) |
|
|
|
Apply updates using the AppLife Update engine |
|
|
|
|
| |
|
Apply updates using your own custom update executable |
|
|
|
Easy software license checking integration into update process |
|
|
|
Distribution Framework Features |
Full |
Limited |
|
Use any web or file server |
|
|
|
Download from any ftp, http, https, UNC, or file path |
|
|
|
Download updates in the background |
|
|
|
Resume interrupted downloads |
|
|
|
Publish updates for specific client versions |
|
|
|
Provide specific, localized summary information for each update |
|
|
|
Publish custom data with each update - Consume data in client code |
|
|
|
Choose from all available updates within client-side logic |
|
|
|
Download progress indication with option to cancel |
|
|
|
Coordinated shut down of all application instances |
|
|
|
Automatically detect proxy settings |
|
|
|
Control rollout of updates gradually over time |
|
|
|
Preserved command line parameters on application restart |
|
|
|
Configurable text to display when no updates are available |
|
|
|
Flexible determination of current client version |
|
|
|
Designate updates with toggle-able limited availability for testing |
|
|
|
Dynamic control of update location |
|
|
|
Security Features |
Full |
Limited |
|
Cryptographic update package signature verification after download |
|
|
|
Secure download support using SSL (https) |
|
|
|
Download and Publish updates from secured network folders |
|
|
|
Securely elevate privileges to apply updates for non-admin client users |
|
|
|
Update without Vista UAC prompting |
|
|
|
Application Update Activity Features |
Full |
Limited |
|
Maintain client system integrity with transacted update execution engine |
|
|
|
Preemptive permission checking to avoid inevitable execution failure |
|
|
|
Replace client files in common folder locations |
|
|
|
Automatically determine files to include in updates |
|
|
|
File mask exclusion of files (e.g. *.config, *.pdb, etc.) |
|
|
|
Add files by mask (e.g. *.exe, *.dll, etc.) |
|
|
|
Create file shortcuts |
|
|
|
Register / unregister 32 or 64 bit COM components |
|
|
|
x64 File System and Registry support |
|
|
|
Update databases using transacted, provider-independent actions |
|
|
|
Modify Xml files (including application config files) |
|
|
|
Start/Stop Windows Services |
|
|
|
Pass variables between update actions |
|
|
|
Simple branding and text customization of update engine user interface |
|
|
|
Optionally restart application after update |
|
|
|
Updates can be applied silently |
|
|
|
Extensible update infrastructure for creating custom actions |
|
|
|
Expansion variables evaluated on the client at runtime |
|
|
Acquiring and Applying a License
Number