Never mind the renaming issue, I'm not worried about that anymore.
Thank you for all your help, let me recount what I have done since having a project that installed flawlessly on 32bit windows.
Probably more for my own understanding then anything else.
My original java product is AFS
The additional one is AFS64
- In order to install on 64bit windows and use a 64 bit jre, I had to create an additional java product (AFS64), the only difference being that the 64-bit application is checked on the new one.
- AI does not allow this new Java Product to be named the same thing as the existing one.
- Then following the directions on
http://www.advancedinstaller.com/user-g ... files.html
- I followed the first bulleted list on this page and added the NOT VersionNT64 to the condition field for my original exe of my original java product (AFS)
- For the second bulleted list on this page, I created a folder under Application Folder, checked the Install folder content into the parent folder option.
- The next step is "add the 64-bit "MyApp.exe" file in this custom folder" which I did, the difference being that the new java product (AFS64) that I created is not named the same as the original, so the file
that I added to this directory is the aijclw.exe of the new java product (AFS64) I don't see a way to add the exe directly.
- Than I go to that component and add the VersionNT64 condition.
- So, one or the other gets installed based on VersionNT64, I added Application & Desktop Shortcuts for the new java product (AFS64)
This is all working correctly at this point, please let me know if the above steps I took are correct or if their is an easier way or something that I am missing.
The only remaining problem I have is launching the application (AFS or AFS64) after the user clicks finish on the exit dialog of the installer.
This is done by using the finish tab - launch application, which points to the exe of the original java product (AFS) so right now it doesn't work when the new java product (AFS64) is the one that was install on a 64 bit windows pc, for course, because the original java product is not the one that was installed in this case.
I did not see a way to condition which exe to launch from the finish actions tab. That lead me down the path to creating two custom actions (which I can condition) which I added to the InstallFinalize standard action. This works, but changed the behavior of the installation to something less than optimal. With these custom actions in place, my application is launched at the end of the ProgressDlg, leaving the installer running in the background. Once the user exits out of my application, the installer displays the ExitDialog and the user clicks finish.
My remaining question is:
Is there a way to:
1. Condition which exe gets launched from the ExitDialog - Finish Actions tab OR
2. Move the execution of the custom actions to a different phase? Is there a phase that would allow the custom actions to execute after the Exit Dialog finish is clicked? Then I could just remove the launch checkbox and always have the application launch.
Sorry this post ended up so long.
Again, thanks for all your help.
FOLLOW US
Get the latest news in Application Packaging