User manual SYMANTEC WISESCRIPT EDITOR FOR NS 7.0 SP2 V1.0

[. . . ] WiseScript Editor Reference WiseScript Editor The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version 7. 0. 2 Legal Notice Copyright © 2010 Symantec Corporation. Symantec, the Symantec Logo, and Altiris are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U. S. Other names may be trademarks of their respective owners. [. . . ] Enter 0 to append to the end of the file. Information in the Search for Existing Text area overrides any line number that is specified here unless the text is not found. Search for Text Enter the text to search for. If more than one line in the file matches, only the first is edited. Comment Text Enter comment to insert at the beginning of the found line. When replacing an existing line, use this to leave the existing line in place but inactive. Set Insert WiseScript Editor Reference 73 Action to insert before the existing line so that subsequent installations find and edit the active command, not the commented line. Insert Action Select the action to be taken when a line is found. Match Criteria Select how the line is matched with the text in Search for Text. Ignore White Space Mark this to ignore spaces and tab characters. Case Sensitive Mark this to make the match case-sensitive. Make Backup File Mark this to make a copy of the text file before editing it. A number is appended to the end of the file name for the backup copies (example: text. 001, text. 002, and so on). The sample scripts Add Tnsnames entry. wse and TextFile. wse use this action. For details on sample scripts, see ScriptHelp. htm in the Samples subdirectory of this product's installation directory. Install File(s) This action installs files on the destination computer. Each file or directory to be installed must have a separate Install File(s) action. When you're installing files permanently on the destination computer using the Install File(s) script action, you might also want to make sure that the destination computer has enough disk space available for these files. Do this using the Check Disk Space script action. The results from an Install File(s) action are put into a variable, INSTALL_RESULT. See its description in Automatic Run-time Variables on page 132. To complete the dialog box Source Pathname Specify the path of the file on your computer. You can use wildcards in this field to indicate that all the files in a directory that match a certain pattern should be installed (example: C:\Dev\*. exe). You can also use compiler variables, but you should not use run-time variables, because this field is used at compile time. [. . . ] Do not put a space between the /d and the compiler variable name. Defines compiler variables from a text file for this run only. The format for the text file is _VAR_=value, with one entry per line. You can use the /s option with this option. /c /d=file. txt Examples: Compiling a . WSE file while defining a compiler variable named _PATH_: "product_installation_directory\Wise32. exe" /d_PATH_=C:\Test /c "C:\Development\Application. wse" Compiling a . WSE file while setting compiler variables defined in a text file named Compile. txt: "product_installation_directory\Wise32. exe" /c /d=C:\Development\Compile. txt "C:\Development\Application. wse" Automated build process You can use command-line options in conjunction with other processes to create an automated build process. [. . . ]