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 packages
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
‎Dec 07, 2010
01:30 PM
Chained msi packages
Hello folks.
I'm having a bit of trouble understanding the documentation as it relates to Chained .MSI packages.
I have two applications.
Application1 installs and then application2 installs.
(Application2 is the "chained" .msi)
The issue I'm having, deals with caching the .msi for application2.
So that I can perform a repair of Application2 after it has been installed.
I can get both Application1 and 2 installed on the target pc.
But if I try to perform a repair on application2, I receive a dialog that indicates it is looking for the temporary folder that held the Application2.msi when both Application1 and Application2 were being installed.
And of course that folder was deleted after the successful install.
I've been trying different settings for the chained package, based on my understanding of the documentation.
But I can't seem to cache the Applicaion2 .msi.
Has anyone been successful with this ?
If so, would you have pity on me and, explain, how you did it ?
As in, what exactly does your Chained package settings look like.
(Cuz I'll try and replicate your setting in my project.)
Thanks in advance for any responses.
I'm having a bit of trouble understanding the documentation as it relates to Chained .MSI packages.
I have two applications.
Application1 installs and then application2 installs.
(Application2 is the "chained" .msi)
The issue I'm having, deals with caching the .msi for application2.
So that I can perform a repair of Application2 after it has been installed.
I can get both Application1 and 2 installed on the target pc.
But if I try to perform a repair on application2, I receive a dialog that indicates it is looking for the temporary folder that held the Application2.msi when both Application1 and Application2 were being installed.
And of course that folder was deleted after the successful install.
I've been trying different settings for the chained package, based on my understanding of the documentation.
But I can't seem to cache the Applicaion2 .msi.
Has anyone been successful with this ?
If so, would you have pity on me and, explain, how you did it ?
As in, what exactly does your Chained package settings look like.
(Cuz I'll try and replicate your setting in my project.)
Thanks in advance for any responses.
(6) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 08, 2010
10:26 AM
Thanks for the reply.
I've attached a .bmp that shows what my settings look like.
I'm very confused.
Both of my applications install fine. (A GOOD thing.)
If I perform a repair on application1, Windows Installer remembers the source location for it (the .msi) and, if available, successfully completes the repair.
If I perform a repair on application2, Windows installer informs me that it can't find the temp file from which Application2 was installed.
And that would be correct.
Cuz it's gone.
I'm puzzled as to what in the wide wide worlds of sports, the "help" text is trying to say.
Any additional ideas would be appreciated.
I've attached a .bmp that shows what my settings look like.
I'm very confused.
Both of my applications install fine. (A GOOD thing.)
If I perform a repair on application1, Windows Installer remembers the source location for it (the .msi) and, if available, successfully completes the repair.
If I perform a repair on application2, Windows installer informs me that it can't find the temp file from which Application2 was installed.
And that would be correct.
Cuz it's gone.
I'm puzzled as to what in the wide wide worlds of sports, the "help" text is trying to say.
Any additional ideas would be appreciated.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 09, 2010
11:02 PM
can you make a new child msi and attach it to the chained installer.Please try this...
I did the same senario as u have mentioned and i was able to repair the child msi also.
I did the same senario as u have mentioned and i was able to repair the child msi also.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 10, 2010
03:41 PM
Thanks for the reply.
Although I'm more than willing to try anything ........
I'm unsure what a child .msi is and how I would go about attaching it.
Can I ask for a little detail so that I might know how to proceed ?
Although I'm more than willing to try anything ........
I'm unsure what a child .msi is and how I would go about attaching it.
Can I ask for a little detail so that I might know how to proceed ?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 15, 2010
06:29 AM
Apologies, I was a little hasty in my last reply.
To make sure the chained msi is cached in the proper place, it needs to have [LocalAppDataFolder]{ProductCodeGUID}\ as its run-time path, like so:
![](/legacyfs/online/vb/8860_Skjermbilde2.JPG)
This will make sure Add/Remove Programs finds the msi in the proper location for reparation, modification and uninstall. (I think..:)
To make sure the chained msi is cached in the proper place, it needs to have [LocalAppDataFolder]{ProductCodeGUID}\ as its run-time path, like so:
This will make sure Add/Remove Programs finds the msi in the proper location for reparation, modification and uninstall. (I think..:)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 19, 2011
10:31 AM
Are you copying the msi to [LocalAppDataFolder]{ProductCodeGUID}\ during the install? How does the msi get to this location on the target machine?
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)