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

-9064 DrLocator '%1' already exists<br />

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

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

converted.<br />

-9065 CompLocator '%1' already<br />

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

project. The Windows Installer<br />

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

-9069 Windows Installer properties<br />

that resolve to 64-bit locations<br />

are not supported in this<br />

edition of <strong>InstallShield</strong>. The<br />

folder '%1' was converted to<br />

'%2'.<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 particular file or folder search and you import that<br />

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

folder search with that same name. 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 Requirements view to<br />

ensure that the file or folder search 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 file or folder search and you import that<br />

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

folder search with that same name. 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 Requirements view to<br />

ensure that the file or folder search that is identified in the warning<br />

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

<strong>Edition</strong>: Support for Windows Installer properties that resolve to<br />

64-bit locations is available in the following editions of<br />

<strong>InstallShield</strong>:<br />

• Premier<br />

• Professional<br />

This warning occurs if the DefaultLocation property in your Visual<br />

Studio project uses a 64-bit location ([ProgramFiles64Folder],<br />

[CommonFiles64Folder], or [System64Folder]) and if you<br />

indicate in the Visual Studio Deployment Project Import Wizard<br />

that you want to import the INSTALLDIR value from your Visual<br />

Studio project. If this warning occurs, <strong>InstallShield</strong> <strong>Express</strong> <strong>Edition</strong><br />

uses the 32-bit equivalent of the folder (for example,<br />

[ProgramFilesFolder]). The Premier and Professional editions<br />

use the 64-bit location.<br />

If you require 64-bit support in your installation, consider<br />

upgrading to the Premier or Professional editions of <strong>InstallShield</strong>;<br />

these editions enable you to create 64-bit packages, install to 64bit<br />

locations, and configure other 64-bit related settings.<br />

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

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

Saved successfully!

Ooh no, something went wrong!