OverviewWhat Is ConvertedWhat Is Not Converted
This section will outline all of the information that gets converted from TrueUpdate 1.0 to TrueUpdate 3.0. For a list of options that are not converted, please see the next section, What Is Not Converted.
This topic covers the conversion in the following areas of a TrueUpdate 1.0 project:
The General Information settings are converted to the following TrueUpdate 3.0 Session Variables:
Product name = %ProductName%
Company name = %CompanyName%
Company URL = %CompanyURL%
Company phone = %CompanyPhone%
Copyright notice = %Copyright%
All of the above session variables can be found on the Session Variables tab. You can access the Session Variables tab by selecting Project > Session Variables... from the program menu.
The server file locations are converted to settings located in two areas in TrueUdate 3.0: TrueUdate servers and automatic upload locations.
This conversion is basically a one-to-one conversion with three differences:
Server file locations in TrueUpdate 1.0 did not have an ID, so the location specified in the v1.0 project is used as the ID in v3.0.
In TrueUpdate 1.0 you needed to specify the full path and filename of the server file, whereas in v3.0, you only need to specify the folder where the server configurations files will exist. The conversion process will drop the filename from the server file location.
Server file locations in TrueUpdate 1.0 have conditions associated with them, however since TrueUpdate servers do not have conditions associated with them in v3.0, this setting is not converted. Instead, TrueUpdate runs through the server locations given the order on the TrueUpdate Servers dialog, until one server is successfully accessed.
Automatic upload locations are a new feature in TrueUpdate 3.0, and usually correspond to the TrueUpdate servers that have been defined. So during the conversion process, TrueUpdate will convert the server file locations into approximate automatic upload locations. Since many of the parameters required by the automatic upload locations are not available in TrueUpdate 1.0, a "best guess" attempt at these settings is made. As a result, it is important to edit each automatic upload location after the conversion process has completed.
The interface is one of the most obvious differences between TrueUpdate 1.0 and 3.0. One of the design goals of version 3.0 was to increase both the work flow, and ease of use of the user interface.
The dialog interface will not be converted into TrueUpdate 3.0 since there is not an applicable interface. If your project used the dialog interface, it is necessary to convert this manually using Dialog actions. Please see the project wizard, or one of the many templates in TrueUpdate 3.0 for information on how to accomplish this.
All of the wizard interface screens will be converted into TrueUpdate 3.0, even if they were not enabled in TrueUpdate 1.0. If they were not enabled in TrueUpdate 1.0, they will be converted to the "Excluded Wizard Screens" screen list. The Update Canceled screen will be converted to the "Excluded Wizard Screens" screen list, even if it is enabled. Due to the new, more configurable user interface in TrueUpdate 3.0, all enabled screens will be converted into screen lists on either the client side or server side.
The images associated with screens in TrueUpdate 1.0 are not converted due to the addition of the themes in v3.0. Instead, the converted screens will all be set to use the default project theme.
Since the dialog interface is not converted, the Default Run Mode setting is not converted either.
The custom icon will be converted over to TrueUdpate 3.0.
The user configuration settings are not converted over into TrueUpdate 3.0, as they are not required for the most part.
Only the messages associated with wizard screens are converted into TrueUpdate 3.0. This preserves any text that you associated with screens in TrueUpdate 1.0, along with the any multilingual support that you added.
All languages that are supported in your TrueUpdate 1.0 project will also be supported in the converted project.
Custom variables are either converted into Lua variables or session variables in TrueUpdate 3.0. For the most part they will be converted into Lua variables unless they are overriding built-in session variables in TrueUpdate 3.0. All variables will have their values assigned at the beginning of the Client Script.
The output folder and the client executable filename will convert properly into TrueUpdate 3.0.
Debug mode is not converted into TrueUpdate 3.0 because there is no equivalent setting. Instead, debugging actions are available.
When working with the Server File Editor in TrueUpdate 1.0, versions were identified by creating version identifiers and then associating a series of actions that were executed when that version was identified.
This general framework is converted for you by converting the actions from each version, into script tabs in TrueUpdate 3.0. The name of each script tab will be the version label, providing it is unique. If it is not unique, a numeric index is appended to its name. Then all of the actions that were on the actions tab will be converted into TrueUpdate 3.0 actions on that script tab.
Version identifiers are converted to If statements on the Server Script which will determine which script tab to run.
The update size associated with each version is converted to a SessionVar.Set action that will set the session variable %UpdateSize% to be whatever was entered in the Update size field of the v1.0 project.
Most actions from TrueUpdate 1.0 are converted over to TrueUpdate 3.0 with a few exceptions that are listed in the What Is Not Converted topic.