Table of Contents
Advertisement
Importing an Installation From a Visual Studio Project
Windows Installer Editor Reference
These tools are not designed to set up a remote automation or a DCOM™ server
automatically.
Use the following procedure to create a Windows Installer package from a Visual Basic,
Visual C#, or Visual J# project, version 2003 or earlier.
See
Import Visual Studio Projects
To import from a Visual Studio project
1.
Do one of the following:
Select File menu > New. On the New Installation File dialog box, select Import
Tools from the Categories list, and in the Templates/Tools list, double-click
the type of project to import. This creates an installation that contains only the
information from the imported installation.
Select Tools menu > Import Tools and select the type of project to import. This
adds the imported installation's information to the current installation file.
The Project or Solution File dialog box appears.
2.
In Project or Solution File, specify the path to the project or solution file and click
Next.
(Visual Basic .NET, C#, or J# projects.) The Select Configuration dialog box
appears. This displays the configurations that are in the solution or project,
which correspond to build configurations in your Microsoft development
environment.
a. Select the configuration to import.
b. To be prompted at the end of this wizard to select which assembly
dependencies get added to which feature, clear Automatically add
Assembly Dependencies without prompting. Otherwise dependencies
are added silently.
(Visual Basic 5 or 6 project.) The Select Visual Basic Directory dialog box
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 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
on page 352.
Tools
353
Advertisement
Table of Contents
Troubleshooting
