OverviewTrueUpdate ServersSession VariablesThemeOptionsAdvanced
An exciting new feature of TrueUpdate 2.0 is the client's ability to update itself if a newer version becomes available. There are two parts in the client that may be updated: the client executable and the client data file. They are both part of the server configuration files that are updated each time a build is done. While TrueUpdate is able to update these files, they may exist in a location where the end user does not have write access. These settings allow you to configure how TrueUpdate should proceed if faced with this situation.
Tip: If the client executable or client data file is updated, the update process must be restarted. You can use the global variable _ClientRestarted to tell whether or not the client was restarted.
What should TrueUpdate do if a newer version of the client executable exists, but the folder is not writable. Choose from:
Notify the user that they do not have the appropriate permissions to update the client by showing and dialog and aborting the update process.
Ignore the new version of the client executable and continue by running the current copy.
Download the new version of the client executable to a temporary location (Windows Temp folder) and run it from there.
Note: Choosing this option may cause your update to function incorrectly if you are referencing files from your update that rely on the client's location such as _SourceFolder or %SourceFolder%.
What should TrueUpdate do if a newer version of the client data file exists, but the folder is not writable. Choose from:
Notify the user that they do not have the appropriate permissions to update the client by showing and dialog and aborting the update process.
Ignore the new version of the client data file and continue by running the current copy.
Download the new version of the client data file to a temporary location (Windows Temp folder) and run it from there.