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
- :
- Re: Multiple Instance support
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 23, 2008
03:07 PM
Multiple Instance support
Thanks to the InstallShield team for providing this support.
A couple questions on the new Multiple Instance support with Basic MSI projects:
1) when specifying another install instance I want to provide an alternate default install directory. I tried setting the INSTALLDIR property within the new Instance properties but when I run the installer I get Microsoft Install error 1606 "Could not access network location [2]" where [2] is [ProgramFilesFolder]MyFolder. It looks like the property ProgramFilesFolder is not getting expanded. Is there any way around this?
2) is there any way to dynamically set the name of the Taskbar and Desktop shortcuts? I tried to use the property [ProjectName] but it did not expand at install time. Again, for multiple instance support I would like to configure a new shortcut with a different name.
A couple questions on the new Multiple Instance support with Basic MSI projects:
1) when specifying another install instance I want to provide an alternate default install directory. I tried setting the INSTALLDIR property within the new Instance properties but when I run the installer I get Microsoft Install error 1606 "Could not access network location [2]" where [2] is [ProgramFilesFolder]MyFolder. It looks like the property ProgramFilesFolder is not getting expanded. Is there any way around this?
2) is there any way to dynamically set the name of the Taskbar and Desktop shortcuts? I tried to use the property [ProjectName] but it did not expand at install time. Again, for multiple instance support I would like to configure a new shortcut with a different name.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 23, 2008
03:37 PM
I use a Type 51 CA scheduled before costing to transform the [INSTALLDIR] property.
As for shortcuts, MSI Shortut table isn't formattable. A custom action will be required. The two approaches I've used are:
1) Don't use Shortcut and just use InstallScript to create/remove the shortcuts
2) Update the Shortcut table dynamically at runtime to tweak the name.
As for shortcuts, MSI Shortut table isn't formattable. A custom action will be required. The two approaches I've used are:
1) Don't use Shortcut and just use InstallScript to create/remove the shortcuts
2) Update the Shortcut table dynamically at runtime to tweak the name.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 24, 2008
03:21 PM
Thanks for the tips. I will have to brush up on some of these more advanced topics.