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
- :
- Desktop shortcut is reused on Multi-Instance install
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 18, 2010
03:33 PM
Desktop shortcut is reused on Multi-Instance install
I am running InstallShield 2010 with a Basic MSI project that supports Multi-Instance installations. When I install the first (default) instance a desktop icon is created pointing to that instance. When I subsequently install a second instance, I was expecting a new desktop icon to be created pointing to the second instance with the default instance icon left untouched. Instead I see that only one icon exists and the directory for that icon now points to the 2nd instance. It seems that the desktop icon takes the instance of the last install.
Is there any way to get multiple desktop icons to appear for a multi-instance installs?
Rob
Is there any way to get multiple desktop icons to appear for a multi-instance installs?
Rob
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 18, 2010
07:03 PM
Unfortunatly Windows Installer doesn't allow formatting of the shortcut name. You'll have to use a custom action to create the shortcuts with transformed names based on the instance.
The cleanest way I've ever found to do it is not author the shortcut in the installer. Instead use a custom action to emit temp rows into the shortcut table at install time and then let MSI create the shortcut as if you had authored it.
The less clean way is to just use a custom action to create the shortcut but then you have to be sure to handle your normal install, uninstall, repair, rollback type stories.
The cleanest way I've ever found to do it is not author the shortcut in the installer. Instead use a custom action to emit temp rows into the shortcut table at install time and then let MSI create the shortcut as if you had authored it.
The less clean way is to just use a custom action to create the shortcut but then you have to be sure to handle your normal install, uninstall, repair, rollback type stories.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 21, 2010
09:54 AM
Thanks for your reply.
Just so I get this straight, on your preferred solution, create a dll that gets launched as a custom action that adds the shortcut entry to the shortcut table. MSI will pick this up automatically during the intall.
thanks.
Just so I get this straight, on your preferred solution, create a dll that gets launched as a custom action that adds the shortcut entry to the shortcut table. MSI will pick this up automatically during the intall.
thanks.