Symantec WISESCRIPT PACKAGE EDITOR 7.0 SP2 - FOR WISE INSTALLATION STUDIO V1.0 Installation Manual page 243

WiseScript Package Editor Reference
This tool only supports projects of file type .VBP. Only ActiveX EXE, Standard EXE,
and ActiveX DLL project types are supported.
Verify that the necessary files and dependency files required by the VB application
are available.
Verify that the files that require self-registration are marked to self-register. To
check this, view the properties of the file, and if the version section contains Ole Self
Register, then the file must be self-registered. A file might fail self-registration
because it doesn't need to be registered, because it's missing a dependent file,
because it might require regsvr.exe to be run manually, or because it is corrupt.
There is no link between a VB 5 or 6 project or solution and the installation you
create for the project or solution. If your solution or project is updated with new
files, you must make those changes in the installation manually.
This tool is not designed to set up a remote automation or a DCOM™ server
automatically.
Note
Files that you specify in System .DLLs to Exclude in Preferences are ignored.
See Setting Preferences
To create an installation based on a Visual Basic project
1. Select Tools menu > Import Visual Basic Project. This adds the imported
installation's information to the current installation file. This is the same as selecting
File menu > Import > Visual Basic Project.
The Project File page appears.
2. In VB Project File, specify the path to the project file and click Next.
The Select Visual Basic Directory page appears.
Specify the directory on your computer where Visual Basic 5 or 6 is installed. This
directory contains the support files that must be included in the installation because
they are needed by the Visual Basic program.
3. Click Next.
The Scanning Project Files page appears. During or after the scan, additional
prompts and pages might appear:
If the project is out of date or missing, a prompt appears. You can try to rebuild
the project from this tool, or open the development environment and rebuild
the project from there.
If the project has a reference to another project, an error message appears and
the import ends. Restart the import and select the solution file (.SLN) that
contains both projects.
If dependency files (.DEP) for Win32 target files are missing, the Dependency
Files Not Found page appears. Dependency files list referenced files. This page
usually does not apply to .NET projects, which use assembly manifests instead
of dependency files, unless the .NET project depends on a COM .DLL that has a
dependency. If the dependency files cannot be read, then the files they refer to
cannot be added to the installation you are creating.
If any files on the Dependency Files Not Found page are crucial to this
installation:
on page 25.
Tools
243