Windows Installer Editor Reference
397
Tools
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. Go to
To complete the import in either editor
on page 397.
To start the import in the Visual Studio integrated editor
1. Select File menu > New > File. In the left pane, click Wise Files and in the right
pane, double-click Import Visual Basic. This creates an installation that contains
only the information from the converted installation.
The Project File dialog box appears.
2. In VB Project File, specify the path to the project file and click Next.
The Select Visual Basic Directory dialog box appears.
3. 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.
To complete the import in either editor
1. Click Next on the Select Configuration or Select Visual Basic Directory dialog box.
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:
a. Cancel the import.
b. Locate the files and move them to the System or System32 directory.
c. Restart the import.
2. Click Next.
If target files were not found during the scan, the Files Not Found page appears.
Files might be missing if the configuration of the solution that you selected has not
been built. Missing files will cause compile errors in the installation that results from
this import process.
Otherwise, the Installation Files page appears.
3. If the Files Not Found page appears:
