AppLife Update version 1.1 is moving along and should be released by Oct 1st. This next release will add many new features as well as strengthen existing features. Here is a list of the noteable features that you can look forward to in version 1.1

Localization of the update controller and update engine user interface in German, Italian, Spanish, French, Japanese, and Chinese (Traditional). With this infrastructure in place, additional languages can be added. If you need a different language and are willing to perform the string translations, we can build a culture assembly for you. Localized custom action assemblies are also supported.

SSL Support and Authentication to your update location. Connect to your update server using HTTPS. You can also authenticate with your update server using Domain/Username/Password settings.

Update Asp.Net applications. Add an asp.net user control that allows you to provide single click update capabilities into your asp.net applications.

x64 Operating System Compatibility. The applife update engine and update service is now completely x64 compatible. You can also set explicit targets for the x86 or x64 file system and registry locations within your updates.

Database Actions Included. Update databases during an update using these provider independent transactable database actions. New actions are Begin Database Transaction, Commit Database Transaction, Transacted Database Query, and Transacted Stored Procedure.

Share Properties between actions. Use the new Read Registry Key action, Read Xml Node action, or Scalar database action to get information that you can use with other update actions. This feature reduces the scenarios where custom actions might be necessary.

Additional control over the Update Engine user interface. You can update your apps without the update engine user interface being shown, you can set the update engine user interface to close immediately after the update completes (no OK button click necessary, but still a progress bar and detail text during the update), you can define your update to supress the automatic application restart wehn the update completes.

Enable setting the Normal/Limited update flag from the command line utility. This allows automating the step of changing an update from limited availability to normal availability.