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: rebuilding/rerelease an MSP = bad idea?
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
‎May 20, 2008
07:46 AM
rebuilding/rerelease an MSP = bad idea?
I'm using InstallShield 2008 and being asked to rebuild and then release an MSP that has already been released to our customers. The originally released MSP contained an incorrect path within a .config file.
Am I correct in thinking this would be a bad idea?
Thanks 🙂
Am I correct in thinking this would be a bad idea?
Thanks 🙂
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 20, 2008
10:47 AM
There are at least two main pain spots with that approach, and possibly more I'm not thinking of. First, if you just rebuild the msp similarly to how you built the first, there's no obvious path for customers who installed the first to be able to install the second. Second, just like there's no path from Patch1v1 to Patch1v2, there will be no good path from all three (RTM, 1v1, 1v2) to Patch2, should you ever release a later cumulative patch.
So you should at least examine (and by examine, I mean build a fake patch and test what happens with various patch application orders) releasing v2 as a cumulative patch so the upgrade line looks like RTM -> v1 -> v2 (-> Patch 2), where v2 and a later Patch2 are both cumulative patches that can patch any previous version.
So you should at least examine (and by examine, I mean build a fake patch and test what happens with various patch application orders) releasing v2 as a cumulative patch so the upgrade line looks like RTM -> v1 -> v2 (-> Patch 2), where v2 and a later Patch2 are both cumulative patches that can patch any previous version.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 20, 2008
02:22 PM
Thanks for you reply.
My support people already helped our customers with Patch1v1 with a self-extracting zip to drop in the correct config file.
Patch1v2 applies correctly against the RTM. A test Patch2 applies correctly against Patch1v2. I'm not familiar with how to make a cumulative (muli-targeted) patch; is there a guide or article you can direct me to?
Thanks!
My support people already helped our customers with Patch1v1 with a self-extracting zip to drop in the correct config file.
Patch1v2 applies correctly against the RTM. A test Patch2 applies correctly against Patch1v2. I'm not familiar with how to make a cumulative (muli-targeted) patch; is there a guide or article you can direct me to?
Thanks!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 21, 2008
10:05 AM
I'm sure there are articles around, but I don't have a favorite. The basic step is to add additional previous releases in your patch design view.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)