This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Bug: Creating Shortcut on Vista
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 09, 2008
09:07 AM
Bug: Creating Shortcut on Vista
My Basic MSI Package creates shortcuts among other things. Installing it on Win XP, everything's fine.
But when installing the package on Vista, the target path isn't correctly translated:
In IS2008:
target = "[INSTALLDIR]Prg\WinApp\MyApp.exe"
working directory = "{WinApp}[INSTALLDIR]Prg\WinApp"
Installing the package on Vista for ex. to InstallDir "C:\Temp" sets the shortcut's target to "C:\Prg\WinApp\MyApp.exe" (which is wrong - "Temp" is missing) and the "Start in" to "C:\Temp\Prg\WinApp" (which is correct).
Any ideas? A new bug?
But when installing the package on Vista, the target path isn't correctly translated:
In IS2008:
target = "[INSTALLDIR]Prg\WinApp\MyApp.exe"
working directory = "{WinApp}[INSTALLDIR]Prg\WinApp"
Installing the package on Vista for ex. to InstallDir "C:\Temp" sets the shortcut's target to "C:\Prg\WinApp\MyApp.exe" (which is wrong - "Temp" is missing) and the "Start in" to "C:\Temp\Prg\WinApp" (which is correct).
Any ideas? A new bug?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 09, 2008
12:48 PM
The Target field of a shortcut is resolved by Windows Installer at runtime. I'm not sure why MSI would exclude C:\Temp from the target path, unless INSTALLDIR contained an incorrect value (unlikely, though, since the working directory is correct).
You may want to try logging the installation to see if INSTALLDIR is changing unexpectedly at any point and to see what the CreateShortcuts action is doing. Another thing you might try is to run full MSI validation against your built MSI package to ensure there aren't any errors with the Directory or Shortcut tables (ignoring ICE43 and ICE57 if you aren't using advertised shortcuts).
You may want to try logging the installation to see if INSTALLDIR is changing unexpectedly at any point and to see what the CreateShortcuts action is doing. Another thing you might try is to run full MSI validation against your built MSI package to ensure there aren't any errors with the Directory or Shortcut tables (ignoring ICE43 and ICE57 if you aren't using advertised shortcuts).