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: How to Repackage a Patch
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
‎Aug 26, 2008
08:34 AM
How to Repackage a Patch
I have a legacy setup EXE and also a few patches that are also EXE.
Goal: Repackage the legacy setup EXE into MSI form, this would serve as the base installation. Repackage each patch into a separate MSP to apply, and uninstall if desired.
How can this be accomplished? The methods listed below have both yielded many validation errors.
I have tried:
- repackaging the base into an MSI, then capturing that MSI plus patch EXE to use for building a patch
- repackaging the legacy EXE into an MSI, then repackaging the legacy EXE plus patch EXE to use for building a patch
Goal: Repackage the legacy setup EXE into MSI form, this would serve as the base installation. Repackage each patch into a separate MSP to apply, and uninstall if desired.
How can this be accomplished? The methods listed below have both yielded many validation errors.
I have tried:
- repackaging the base into an MSI, then capturing that MSI plus patch EXE to use for building a patch
- repackaging the legacy EXE into an MSI, then repackaging the legacy EXE plus patch EXE to use for building a patch
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 27, 2008
05:25 AM
aaronboock wrote:
I have a legacy setup EXE and also a few patches that are also EXE.
Goal: Repackage the legacy setup EXE into MSI form, this would serve as the base installation. Repackage each patch into a separate MSP to apply, and uninstall if desired.
How can this be accomplished? The methods listed below have both yielded many validation errors.
I have tried:
- repackaging the base into an MSI, then capturing that MSI plus patch EXE to use for building a patch
- repackaging the legacy EXE into an MSI, then repackaging the legacy EXE plus patch EXE to use for building a patch
Could you send me you ism so I can take a peek?
reg, Henno
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 27, 2008
02:41 PM
It appears that the errors are caused by component ID's not maching in the Base and Latest MSI's.
What is the recommended process for attacking the situation I am in?
What is the recommended process for attacking the situation I am in?