Windows Installer, Java Installer, Freeware Installer
Home|Contact|Site Map|TOC|Search
Download  Features   Java  Licensing  Purchase  Testimonials  Support  Forums

The Update Properties Page

This page gives you the possibility to configure the update. At build, these settings will be saved in an Updates Configuration File.

Update Properties

Display Name

This is the name for the update that will be displayed to the user. This string can be localized.

"Name" key from the Updates Configuration File

Download URL

The URL from where the update file should be downloaded from.

"URL" key from the Updates Configuration File

The file can also be placed in a location on the local network or local machine. This can be specified with the following syntax: file://location of the file.

Examples:

  • Local network: file://\\computername\path\filename.ext
  • Local computer: file://c:\updates\file.exe

NoteUpdates from local network are not downloaded on the local machine, but are installed from their network location.

Release Date

The date on which this update was released. This entry is necessary if you plan to use the license validity check feature in the Advanced Functionality.

"ReleaseDate" key from the Updates Configuration File

Critical Update

Marks the update as critical. It is used for automatically download and install of some types of updates.

"Flags" key from the Updates Configuration File

Update Installer

File Path

Specify the location of the update file on the disk.

Command Line

Command line parameters to be used when installing this update. For example, using the "/qn" parameter for a MSI update will make it install silently, without any UI.

"CommandLine" key from the Updates Configuration File

Compute MD5 signature from file.

Specify whether you want to use the MD5 signature to check the update file integrity.

"MD5" key from the Updates Configuration File

Attempt to suppress GUI or console

The update will be installed without user interface. This flag is to be used for console applications.

TipIn order to achieve this behavior for MSI update files you can launch them with the "/qn" command line parameter.

"Flags" key from the Updates Configuration File

Installed Detection

In this section you can specify the detection method for the updates. It is used by the updater to determine whether an update is installed or not. If the comparison condition is true, the update is considered installed and its download is stopped.

File

The location of the file that must be present in order for the update process to be considered successful. This string can contain the [APPDIR] value - the path where the application is installed. It can also contain any environment variables, surrounded in with the "%" character. By default, it is checked only the existence of the file. You can improve this by supplying an additional criteria: Version or File Size.

"FilePath" key from the Updates Configuration File

Additional settings:

  • File Size - The size of the file used for comparison. It can be directly specified or you can get it from a file. Use the [ ... ] button to select the file. A match in the file size means that the update is installed.

WarningBecause a mismatch in the file size is automatically viewed as a missing update, you should always use the Replaces field on newer updates. This way you'll avoid older updates being installed just because the file size was different after installing a newer update.

  • Version - The file version used for comparison. It can be directly specified or you can get it from a file. Use the [ ... ] button to select the file.
Registry Value

The location in the registry where the version is stored. You can either specify it directly or use the [ ... ] button to select it.

"RegistryKey" key from the Updates Configuration File

The recommended installed detection criteria is this:

  • in the original installation package you create a registry entry which contains the version of the package (you can use the ProductVersion property)
  • in the "Installed Detection" section of the Updates configuration project use this registry value as a detection criteria
  • you set the version of the update package as the additional criteria

This way the Updater will verify which version of the package is installed.

Additional settings:

  • Version - The version used for comparison. It can be directly specified or you can get it from a file. Use the [ ... ] button to select the file.

Auto Close Applications

In this section you can specify the applications that you want to be closed during the update process.

Adding a new application to the list

Use the [ New... ], the "New" context menu item or press the Ins key. The New Auto-Close Application dialog will appear allowing you to specify a new application

Editing an application from the list

Use the [ Edit... ], the "Edit" context menu item or press the Space key. The Edit Auto-Close Application dialog will appear allowing you to edit an application

Deleting an application from the list

Use the [ Remove ], the "Remove" context menu item or press the Delete key.

Privacy Policy | Windows Installer | Search Engine Ranking | Link Analyzer