Wisescript Conversion Guidelines - Symantec WISE PACKAGE STUDIO 8.0 - REFERENCE V1.0 Reference

WiseScript Conversion Guidelines

Wise Package Studio Reference
Replace @Wininstall With
If source paths in the WinINSTALL text file contain the variable @Wininstall,
specify the value of the variable here. The value you specify replaces all
instances of @Wininstall located in source paths.
Replace @Server With
If source paths in the WinINSTALL text file contain the variable @Server,
specify the value of the variable here. The value you specify replaces all
instances of @Server located in source paths.
7. Click Next.
The conversion process begins, and status messages and major errors appear in the
Conversion Status section.
8. To obtain a record of the conversion errors, click Save Errors or Print Errors.
9. Click Finish to complete the conversion process.
If a file that is part of a merge module is added, the Files in Merge Modules dialog
box appears. It prompts you to add the merge module and, if necessary, download
it.
See Adding Merge Modules Instead of Files
If a file that is used by a package in the Wise Software Repository is added, the Files
in Repository dialog box appears and prompts you to add a version of the file that is
in the repository.
See Adding Files From the Wise Software Repository
10. Open the resulting package in Windows Installer Editor (.WSI or .MSI) or WiseScript
Package Editor (.WSE) to view the converted file and to resolve reported problems.
Pages in Installation Expert, such as the Files page, are populated based on the
contents of the source installation.
Following are guidelines for using Legacy Setup Conversion to convert a WiseScript™
(.WSE) that was created in version 5.0 and later of Wise Installation System or in any
version of WiseScript Editor or WiseScript Package Editor.
If you do not have the original .WSE, you can convert the compiled .EXE instead,
because it contains an embedded copy of the script. You cannot convert all .EXEs—
only .EXEs that were created with one of the applications above.
Because WiseScripts are based on a different technology than Windows Installer,
not all elements of your script are converted to Windows Installer format:
Only the installation of files, registry changes, and other system changes are
converted.
Custom dialog boxes, custom logic, and other settings are not converted.
All the files available to the original WiseScript installation must be available to the
converted Windows Installer installation at the same locations.
Components are converted to features, and Execute Program script actions are
converted to Execute Program custom actions.
Some script actions can cause problems with the conversion process.
Wise Package Studio Tools
on page 232.
on page 144.
116