InstallAware

I have a project that is trying to create a shorcut on the target system and point to a custom icon that is located in my $TARGETDIR$ on the target machine.

In the shortcut properties (in my project), my "Icon File Path" is set to $TARGETDIR$\bpa.ico. It worked fine on the target system when I was compiling the setup project in 32-bit mode. As soon as I try to compile the project with the '64-bit Operating System' option turned on, my icon path is messed up on the target system. When I look at the properties of the shortcut on the target system, it's pointing to "%APPDATA%\Microsoft\Installer\{PRODUCTCODE}\ID_24TARGETDIR245cBPA.ico0.ico".

Any idea why this is happening when compiling for a 64-bit system?

Cheers,

CHRIS

Chris,

Are you testing the 32 and 64 bit versions on the same machines?

Yes, the target machine in both cases is a 64-bit version of Windows 7. I compile my project in 32-bit mode, my shortcut path to the icon file is set up correctly. As soon as I compile the project with the '64-bit operating system' option checked (in Application Requirements), the icon path is incorrect. What's interesting, is the path it's trying to find, is using the product code from the InstallAware project settings (internal msi I suppose), but when I install my product it installs it using the outer msi product code (the one that is generated by using the Group Policy wizard).

Cheers,

C.

Hi,

Can you try creating a new setup from a template to see if the same happens there?

I tried using the 'Win64 Setup' template, and have the same results. As soon as I de-select the '64-bit Operating System' option (in Application Requirements), then the path to the icon is installed correctly.

Thanks. Could you please attach a reproducing project here so we could take a look at this?

I've attached our project file that we're having issues with - let me know if you require anything else.

Cheers,

C.

Hi,

You are not using the native engine (which is turned on by setting the NATIVE_ENGINE variable to TRUE).
When not using the native engine, you cannot use variables in the icon file path.
You did use a variable - $TARGETDIR$ - which is why this is not working.