Table of Contents
Advertisement
Releases Page
Wise Virtual Package Editor Reference
To open an existing WiseScript, click Browse in the lower-left corner and specify
the script.
To create a new WiseScript, add actions from the Actions pane to the
Installation Script pane.
See About Script Editor in the WiseScript Package Editor Help.
5.
When you finish editing the WiseScript, click OK.
The WiseScript appears on the Events page.
Note
When you compile a .WVP file, the syntax of the WiseScript is validated. If the
WiseScript contains syntax errors, a Compile Failed dialog box appears and lists these
errors.
See also:
About Installation Expert
Before you distribute a virtual runtime archive file (.VRA) to end users, you must create
a release for the archive file. A release consists of a WiseScript .EXE wrapper that
contains the logic that is needed to install your application properly.
You use the Releases page in Virtual Package Editor to create a release for a .VRA file.
You can create any number of releases, but normally you would create a single release
for an archive file.
Before you use the Releases page, you should be familiar with the following:
WiseScript project file (.WSE)
When you create a release for a .VRA file, a WiseScript project file (.WSE) is
created, which when compiled creates the .EXE wrapper. The .WSE file contains the
logic needed to install the .VRA file. You can edit this .WSE file from the Releases
page.
See
Editing an Archive File's WiseScript Wrapper
By default, the .WSE file includes installation error messages and several installation
dialog boxes that appear when the end user runs the .EXE. It also includes the
installation's maintenance mode dialogs that appear when the end user clicks the
application's Change/Remove button in Add/Remove Programs.
See
About User Maintenance of Virtual Software Packages
SVS Driver runtime
The SVS Driver runtime (an unlicensed version of the driver) or a compatible
version of the SVS Driver must be installed on the end user's computer before a
.VRA file can be imported into an SVS layer. When you create a release for a .VRA
file, you can add the logic that is needed to install the SVS Driver runtime if a
compatible version of the driver is not found on the end user's computer. You can
include the SVS Driver runtime with your installation or have it downloaded when
your installation runs.
See
Creating a Virtual Software Package Release
on page 14
Creating Virtual Software Packages
on page 34.
on page 11.
on page 33
31
Advertisement
Table of Contents
