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.

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

Error or<br />

Warning<br />

Number Description Troubleshooting Tips<br />

-9057 File key '%1' already exists in<br />

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

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

-9058 Shortcut key '%1' already<br />

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

project. The shortcut '%2' was<br />

not converted.<br />

-9059 Extension '%1' already exists in<br />

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

file type '%2' was not<br />

converted.<br />

Chapter 25: Errors and Warnings<br />

Visual Studio Project Import Errors and Warnings<br />

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

contains a file that is associated with a particular file key and you<br />

import that project into an <strong>InstallShield</strong> project that already<br />

contains a file with that same file key. This scenario may occur if<br />

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

project more than once.<br />

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

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

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

<strong>Edition</strong>: The Premier and Professional editions of <strong>InstallShield</strong><br />

contain a Direct Editor view that shows the file key that is<br />

associated with each file in your project. The file keys are the<br />

primary keys of the File table in the .msi database; the File table<br />

cannot contain duplicate file keys.<br />

You can also see file key information in the Files area of the<br />

Components view in the Premier and Professional editions of<br />

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

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

contains a shortcut that is associated with a particular shortcut<br />

key and you import that project into an <strong>InstallShield</strong> project that<br />

already contains a shortcut with that same shortcut key. 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 Shortcuts/Folders view<br />

to ensure that the shortcut that is identified in the warning<br />

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

<strong>Edition</strong>: The Premier and Professional editions of <strong>InstallShield</strong><br />

contain a Direct Editor view that shows the shortcut key that is<br />

associated with each shortcut in your project. The shortcut keys<br />

are the primary keys of the Shortcut table in the .msi database;<br />

the Shortcut table cannot contain duplicate shortcut keys.<br />

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

contains a particular file extension and you import that project<br />

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

extension. This scenario may occur if you import the same Visual<br />

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

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

ensure that the file extension that is identified in the warning<br />

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

<strong>InstallShield</strong> <strong>2012</strong> <strong>Express</strong> <strong>Edition</strong> <strong>User</strong> <strong>Guide</strong> ISE-1800-UG01 659

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

Saved successfully!

Ooh no, something went wrong!