Replace an existing application file within a TTK and perform a leverage.

Syntax

Catalyst /U UserName [/D] TTKName ReplacementFName [/Replace] [AlternativeFName] [HHPFile:HHPFilename] [Rule:RuleName] [ezLogFile:ezLogFile] [/write] [/open]

Parameters

/U

Update File

UserName

The name that will appear in the history list in the TTK.

/D

Parameter used to select default settings when running a leverage. If this parameter is not present the options currently in the registry will be used. These configuration options be modified using User Profiles.

See Leverage for more information on these defaults.

TTKName

Filename of TTK containing files to be updated.

ReplacementFName

The path on disk to the newer version of the files or folders. The Update Expert will replace existing files in the TTK with the files specified here.

  • When a file is supplied, the Update Expert will match it against a file of the same name within the TTK. The match will occur against the first found file of the same name
  • When a folder from disk is supplied the command will search for a folder matching this name within the TTK. Once a matching folder name is located, the Update expert commences updating the files within the TTK with those from disk. This only updates existing files in the TTK's folder. If extra files are present in the new source folder on disk, those are ignored. To add those files use the /Replace parameter.

/Replace

The matching folder in the TTK is deleted and replaced with the folder to be inserted.

Without the /Replace parameter only existing files in the TTK’s folder will be updated; using this parameter, any extra files in the folder on disk will also be added to the folder in the TTK and leveraged.

AlternativeFName

Parameter used to specify an alternative name for the file in the TTK being replaced.

HHPFile:HHPFilename

If updating a CHM file, it may be necessary to also update the associated project file (or HHP file). This parameter instructs the Update exert to also update the HHP file.

Rule

When inserting a file that needs a rule for parsing, the rule is specified using the Rule parameter.

ezLogFile:ezLogFile

The user can optionally specify a log file to which results of each Catalyst ezScript command are output.

If the log file is not specified by the user or is invalid, the default log file (ezScriptBatchLog.txt in the Public location) is used.

/write

The command line which has been processed by Catalyst will be written into the ezScript batch log file.

This will help to debug your command if something is not behaving as expected.

/open

Launches MS Notepad and displays the content of ezScript batch log when the command finishes.

Examples

Catalyst /U John C:\TtkFiles\Version1Fr.ttk C:\SourceFiles\Version2File.exe Version1File.exe

Catalyst /U John C:\TtkFiles\Version1Fr.ttk C:\SourceFiles\VersionFile.exe

Catalyst /U "%USERNAME%" "C:\Samples\UpdateExpert\MyProjectEn-De.ttk" "C:\Samples\UpdateExpert\WWW\"

Catalyst /U "%USERNAME%" "C:\Samples\UpdateExpert\MyProjectEn-De.ttk" "C:\Samples\UpdateExpert\WWW\VERITAS Software.htm"

Catalyst /U "%USERNAME%" "C:\Samples\UpdateExpert\MyProjectEn-De.ttk" "C:\Samples\UpdateExpert\WWW\WordPerfect.htm"

Catalyst /U "%USERNAME%" "C:\Samples\UpdateExpert\MyProjectEn-De.ttk" "C:\Samples\UpdateExpert\HTML" /Replace