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.
Our licensing model is based on users who actually build update packages. With AppLifeŽ Update, your costs do not increase with more end users, project developers, or even applications. You simply purchase a license for your team members who build update packages. Furthermore, all licenses include one year of premium technical support and software upgrades.
Single Builder License
An AppLifeŽ Update Single Builder license permits one user to install and use the AppLife Update tools on a single computer. A licensed builder can build updates for an unlimited number of applications. The client components deployed with your software can be distributed royalty-free to an unlimited number of clients.
Limited Licensing
AppLifeŽ Update is a very flexible and feature rich application updating framework that meets the needs of even the most complex application updating challenges. Many applications do not require all of the features that AppLifeŽ Update has to offer. For these applications, we offer a limited license. A limited license grants access to the robust application updating framework within AppLifeŽ Update and file replacement features. When you are ready to customize your update process or take advantage of all of the other update actions available, you can extend your update solution at any time by simply purchasing a full license.
Feature Matrix
|
General Features |
Full |
Limited |
|
Complete, built-in update process user interface |
|
|
|
Windows Forms Updating Visual Controls |
|
|
|
WPF Updating Visual Controls |
|
|
|
Comprehensive API to control the update process |
|
|
|
Discrete API methods to check for updates |
|
|
|
Discrete API methods for downloading updates |
|
|
|
Visual Studio Designer Support |
|
|
|
Update Execution Log Viewer |
|
|
|
Integrate update publishing directly into automated build processes |
|
|
|
Localized update process (en, de, es, fr, it, ja, zh-CHT) |
|
|
|
Easily integrate your licensing model into the update process |
|
|
|
Supports the .Net 2.0 through 4.0 Frameworks (Including Client Profiles) |
|
|
|
Full support for Vista/Windows 7 UAC Elevation |
|
|
|
Distribution Framework Features |
Full |
Limited |
|
Use any web or file server |
|
|
|
Manage multiple update locations |
|
|
|
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 |
|
|
|
Pass custom http header values to web server |
|
|
|
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 |
|
|
|
Automatic Update Chaining |
|
|
|
Distribute .Net 4.0 Framework |
|
|
|
Easily execute custom .Net code with the Dynamic Code Action |
|
|
|
Conditional Expressions on Update Actions |
|
|
|
Bitwise File Patching |
|
|
|
Comprehensive Update Logging |
|
|
|
Add and Remove Assemblies from the GAC |
|
|
|
Replace Files on Windows Restart |
|
|
|
Register .Net Assemblies for COM Interop |
|
|
|
Execute Command Line Activity |
|
|
|
Execute MSI's during Update |
|
|
|
Pass Client State Info into Update Process |
|
|
|
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 |
|
|
|
Complete Visual Customization of Update User Interface |
|
|
|
Update Summary Spell Checking |
|
|
|
Updates can be applied silently |
|
|
|
Extensible update infrastructure for creating custom actions |
|
|
|
Expansion variables evaluated on the client at runtime |
|
More: