Windows Installer Editor Reference
352
Tools
6. To obtain a record of any conversion errors, click Save Errors or Print Errors.
7. Click Finish.
More errors might appear at this point, which have to do with saving in Windows
Installer format.
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
on page 112.
8. Open the resulting package in Windows Installer Editor 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. If you converted an .IPF, files are referenced
from their original locations. If you converted an .EXE, files from the converted
installation are stored in and referenced from the extract directory that you
specified above.
See also:
Convert SMS Installer or WiseScript Installation
on page 350
Import Visual Studio Projects
The Import Visual Basic, Visual C#, or Visual J# tools let you import a Visual Basic, C#,
or J# project file into an installation file. You specify information about the project, and
the tool extracts information, such as source file paths, and integrates it into a new or
existing installation.
See
Importing an Installation From a Visual Studio Project
on page 353.
z
These tools only support projects of these types:
Microsoft Visual Basic 5
Microsoft Visual Basic 6
Microsoft Visual Basic .NET, version 2003 or earlier
Microsoft C#, version 2003 or earlier
Microsoft J#, version 2003 or earlier
z
These types of files are supported: .VBP, .VBPROJ, .CSPROJ, .VJSPROJ, or .SLN.
z
When you import a solution, any project types other than those listed above are
skipped. If your VB, C#, or J# projects depend on files that are in projects that are
skipped, the installation might not work.
z
For Visual Basic projects, the Visual Basic Import tool only supports file types of the
Standard EXE project type.
z
For Visual Basic .NET, C#, or J# projects, if a project file has dependencies on other
projects, you cannot import just the project file. You must import the entire solution
that contains the project and its dependencies.
z
There is no link between a 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.