Symantec WISESCRIPT PACKAGE EDITOR 8.0, Справочник

Страница: 29 / 268

WiseScript Package Editor Reference 29
Installation Management
As you edit, the new path appears to the right of the original path in the list box. If
you have moved the entire directory tree that contains the installation files, you
might only need to edit the root directory to change all the references.
4. Mark Change Sub-Directories to update the paths of the subdirectories of the
selected directory.
5. When you finish editing directories, click OK.
All parts of the installation that reference these directories are updated.
Converting to UNC-Based Source File Paths
¾
WiseScript Package Editor only
You can convert the mapped drive paths of source files to UNC-based (Uniform Naming
Convention) paths. This helps prevent compile errors when installation source files are
on a central file server.
Example: If you add files to a script from your Y:\ drive, which is mapped to a file
server, the paths in the installation begin with Y:\. If a co-worker opens and compiles
the script on a computer that doesn’t have its Y:\ drive mapped to the same file server,
the compile fails because the script cannot find the source files on the Y:\ drive.
However, if you first convert all network paths to UNC-based paths, co-workers on the
same network can open and compile the script without encountering errors.Instead of a
path such as Y:\Application.ini, a file has a fully qualified path such as
\\Server\Development\Application\Application.ini.
1. Select Edit menu > Source Directories.
The Change Source Directories dialog box appears and lists all the directories
referenced in the script.
2. From Type, select Change source paths to UNC paths.
3. Click OK. This action cannot be undone.
A one-time conversion of all the network paths in a script is performed. Paths to files
that are on local drives are not converted. All network files you add subsequently are
converted to UNC-based paths.
If you later change Type to Do not modify source paths, the converted paths stay
converted, but new files you add do not have UNC-based paths.
Converting to Relative Source File Paths
¾
WiseScript Package Editor only
You can convert the paths of source files to relative paths. You might do this to keep all
your source files in a central version and source control system. (Example: Microsoft
Visual SourceSafe. In Microsoft Visual SourceSafe, if you copy the installation files to a
different directory each time you do a Get, you can use this feature to ensure that the
paths are always valid, even though the directory structure changes.)
A relative path uses .\ to indicate the current directory, and it uses ..\ to indicate one
directory up. All paths are relative to where the .WSE file is located.