09.12.2012 Views

InstallShield 2012 Spring Express Edition User Guide

InstallShield 2012 Spring Express Edition User Guide

InstallShield 2012 Spring Express Edition User Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 25: Errors and Warnings<br />

Visual Studio Project Import Errors and Warnings<br />

Table 25-6: Visual Studio Project Import Errors and Warnings (cont.)<br />

Error or<br />

Warning<br />

Number Description Troubleshooting Tips<br />

-9053 Launch condition '%1' specifies<br />

no conditions. The launch<br />

condition was not converted.<br />

-9054 File search '%1' specifies no<br />

file names. The file search was<br />

not converted.<br />

-9055 Feature '%1' already exists in<br />

the <strong>InstallShield</strong> project. The<br />

feature was not converted.<br />

-9056 Directory '%1' already exists in<br />

the <strong>InstallShield</strong> project. The<br />

folder '%2' was not converted.<br />

This warning occurs if the Condition property for the specified<br />

launch condition was left blank in the Launch Conditions Editor in<br />

Visual Studio. The warning alerts you that <strong>InstallShield</strong> could not<br />

configure the launch condition during the import or conversion<br />

process.<br />

To resolve this issue, specify a condition in Visual Studio, and then<br />

convert or import the Visual Studio project into an <strong>InstallShield</strong><br />

project. Otherwise, you can add and configure the launch<br />

condition in the Requirements view in <strong>InstallShield</strong> after you have<br />

converted or imported the Visual Studio project.<br />

This warning occurs if the FileName property for the specified file<br />

search was left blank in the Launch Conditions Editor in Visual<br />

Studio. The warning alerts you that <strong>InstallShield</strong> could not<br />

configure the file search during the import or conversion process.<br />

To resolve this issue, specify the file name for the file search in<br />

Visual Studio, and then convert or import the Visual Studio project<br />

into an <strong>InstallShield</strong> project. Otherwise, you can add and configure<br />

the file search in the Requirements view in <strong>InstallShield</strong> after you<br />

have converted or imported the Visual Studio project.<br />

<strong>Edition</strong>: This warning may occur in the Premier and Professional<br />

editions of <strong>InstallShield</strong>.<br />

This warning is not applicable to the <strong>Express</strong> edition; in this<br />

edition, <strong>InstallShield</strong> adds all of the application data from the<br />

Visual Studio project to the Always Install feature in the<br />

<strong>InstallShield</strong> project.<br />

This warning occurs if you have a Visual Studio project that<br />

contains a particular feature and you import that project into an<br />

<strong>InstallShield</strong> project that already contains that feature. This<br />

scenario may occur if you import the same Visual Studio project<br />

into your <strong>InstallShield</strong> project more than once.<br />

This warning occurs if you have a Visual Studio project that<br />

contains a particular folder and you import that project into an<br />

<strong>InstallShield</strong> project that already contains that folder. This<br />

scenario may occur if you import the same Visual Studio project<br />

into your <strong>InstallShield</strong> project more than once.<br />

If you encounter this warning, check the Files view to ensure that<br />

the folder that is identified in the warning message is not missing<br />

from your <strong>InstallShield</strong> project.<br />

658 ISE-1900-UG00 <strong>InstallShield</strong> <strong>2012</strong> <strong>Spring</strong> <strong>Express</strong> <strong>Edition</strong> <strong>User</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!