09.12.2012 Views

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

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 />

-9060 Registry key '%1' already exists<br />

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

registry entry 'Key: %2 Value:<br />

%3 Data: %4' was not<br />

converted.<br />

-9061 Custom action '%1' already<br />

exists in the <strong>InstallShield</strong><br />

project. The custom action<br />

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

-9062 Launch condition '%1' already<br />

exists in the <strong>InstallShield</strong><br />

project. The launch condition<br />

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

-9063 RegLocator '%1' already exists<br />

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

registry search '%2' was not<br />

converted.<br />

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

contains a particular registry entry and you import that project<br />

into an <strong>InstallShield</strong> project that already contains that same<br />

registry entry. This scenario may occur if you import the same<br />

Visual Studio project into your <strong>InstallShield</strong> project more than<br />

once.<br />

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

that the registry entry that is identified in the warning message is<br />

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

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

contains a particular custom action and you import that project<br />

into an <strong>InstallShield</strong> project that already contains a custom action<br />

with that same name. This scenario may occur if you import the<br />

same Visual Studio project into your <strong>InstallShield</strong> project more<br />

than once.<br />

If you encounter this warning, check the Custom Actions view to<br />

ensure that the custom action that is identified in the warning<br />

message is not missing from your <strong>InstallShield</strong> project.<br />

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

contains a particular launch condition and you import that project<br />

into an <strong>InstallShield</strong> project that already contains a launch<br />

condition with that same name. This scenario may occur if you<br />

import the same Visual Studio project into your <strong>InstallShield</strong><br />

project more than once.<br />

If you encounter this warning, check the Requirements view to<br />

ensure that the launch condition that is identified in the warning<br />

message is not missing from your <strong>InstallShield</strong> project.<br />

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

contains a particular registry search and you import that project<br />

into an <strong>InstallShield</strong> project that already contains a registry search<br />

with that same name. This scenario may occur if you import the<br />

same Visual Studio project into your <strong>InstallShield</strong> project more<br />

than once.<br />

If you encounter this warning, check the Requirements view to<br />

ensure that the registry search that is identified in the warning<br />

message is not missing from your <strong>InstallShield</strong> project.<br />

660 ISE-1800-UG01 <strong>InstallShield</strong> <strong>2012</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!