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: Chained MSI Relative Path
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
‎Nov 15, 2011
03:44 PM
Chained MSI Relative Path
I have a chained msi that is installed along with my main msi. I want the chained msi to be installed in a folder along side the main msi.
example
main msi : C:\Program Files\Main Msi\
chained msi: C:\Program Files\Chained Msi\
I tried to use a relative path in the Install properties:
INSTALLDIR = "[INSTALLDIR]..\Chained Msi\"
,but that didn't seem to work. Anybody know how to do this???
This is a basic MSI project
example
main msi : C:\Program Files\Main Msi\
chained msi: C:\Program Files\Chained Msi\
I tried to use a relative path in the Install properties:
INSTALLDIR = "[INSTALLDIR]..\Chained Msi\"
,but that didn't seem to work. Anybody know how to do this???
This is a basic MSI project
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 15, 2012
04:13 PM
Does anyone have a solution for this? You would think this request would be VERY common with Chained MSIs, yet I see that InstallShield hasn't replied, and the original requester never posted a solution.
I tried the intuitive thing of using a relative path based on INSTALLDIR, as did the original requester, but got an error stating that ".." is an invalid path character.
All help is appreciated.
- Matt -
I tried the intuitive thing of using a relative path based on INSTALLDIR, as did the original requester, but got an error stating that ".." is an invalid path character.
All help is appreciated.
- Matt -
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 19, 2012
03:30 PM
Demigod,
I did not ever find a solution to this problem and since it only happened when the user installed the program not in program files I wasn't concerned enough to fix it. A possible solution would be to write a custom script to look up where the main product is installed in the registry and then do some relative parsing on your own, but this assumes that the main product has written out its path to the registry prior to starting the chain msi install.
I did not ever find a solution to this problem and since it only happened when the user installed the program not in program files I wasn't concerned enough to fix it. A possible solution would be to write a custom script to look up where the main product is installed in the registry and then do some relative parsing on your own, but this assumes that the main product has written out its path to the registry prior to starting the chain msi install.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)