InstallShield 2012 Spring Express Edition User Guide

Chapter 25: Errors and Warnings
Visual Studio Project Import Errors and Warnings
Table 25-6: Visual Studio Project Import Errors and Warnings (cont.)
Error or
Warning
Number Description Troubleshooting Tips
-9077 File key '%1' already exists in
the InstallShield project. The
project output '%2' was not
converted.
-9078 The InstallShield project is not
in a Visual Studio solution. The
project output '%1' was not
converted.
-9079 The Visual Studio project '%1'
could not be found in the
current Visual Studio solution.
The project output '%2' was not
converted.
-9080 The project output group '%1'
could not be found in the Visual
Studio project '%2'. The project
output '%3' was not converted.
This warning occurs if you have a Visual Studio project that
contains a project output that has a file that is associated with a
particular file key, and you import that project into an InstallShield
project that already contains a file with that same file key. This
scenario may occur if you import the same Visual Studio project
into your InstallShield project more than once.
If you encounter this warning, check the Files view to ensure that
the file that is identified in the warning message is not missing
from your InstallShield project.
Edition: The Premier and Professional editions of InstallShield
contain a Direct Editor view that shows the file key that is
associated with each file in your project. The file keys are the
primary keys of the File table in the .msi database; the File table
cannot contain duplicate file keys.
You can also see file key information in the Files area of the
Components view in the Premier and Professional editions of
InstallShield.
This error occurs if your InstallShield project is open in
InstallShield, but not from within Visual Studio, and you try to
import a Visual Studio project that contains project outputs into
the InstallShield project.
To resolve this error, open your InstallShield project from within
Visual Studio, and then import the Visual Studio project into it.
If you want to import into an InstallShield project a Visual Studio
setup or merge module project that contains a project output, the
Visual Studio project must be in the same solution as all of its
project dependencies. Otherwise, this error occurs when you try
to import the Visual Studio project.
To resolve this error, ensure that your InstallShield project is in the
same Visual Studio solution that contains the Visual Studio setup
or merge module project that you are importing. In addition,
ensure that the solution also includes all of the other Visual Studio
projects that are dependencies of the Visual Studio setup or
merge module project. Then you can import the Visual Studio
setup or merge module project into your InstallShield project.
This error occurs if you convert a Visual Studio setup or merge
module project that contains a project output group but
InstallShield encounters a problem when incorporating a project
output of that group into the InstallShield project.
To resolve this error, request technical support.
664 ISE-1900-UG00 InstallShield 2012 Spring Express Edition User Guide