/build/static/layout/Breadcrumb_cap_w.png

Combining two patches into one

Howdy,


I have previously released 2 versions of an application (lets call them Version A and Version B) and are about to release a third version (Version C). I would like to release a patch that will patch version A to C or version B to C but cannot find any documentation to cover it.

I can quite easily create a patch to update A to B, a second patch B to C, and a third patch A to C but I would like to combine the three
patches into one. I can imagine my number of patches skyrocketing during future version releases.

I know it is possible because I have used a demo version of MSIStudio to create the PCP and the MSP automatically. The MSP works great (A to B, or B to C) but I really want to create my own MSP from the PCP (even from the one MSIStudio creates would be fine). I can see that the PCP has two TargetImages (A.msi and B.msi) and that the UpgradedImages table has the third image (C.msi) but then I run msimsp.exe:


msimsp -s Patch.pcp -p Patch.msp -l log.txt -d


, I get the following error (and the MSP is not created):


ERROR: This patch contains multiple transform sets and is a mixture of QFE, minor, and/or major patches.


Surely if I have the correct PCP (that MSIStudio created) and I have the same .msi files that MSIStudio used... I should be able to create the same MSP using msimsp? What is MSIStudio doing that I am not? I know it must be using msimsp because the first time I ran it the program produced an error and asked me to manually copy the msimsp executable into the applicaiton folder.


To reiterate... what is MSIStudio doing that I am not?


Additional------>
Does anyone have an example I can follow or has anyone even accomplished this? I want to produce a single patch file (.msp) that will update all previously released versions to the current release. All versions will be minor changes/patches.

thanks,
/evan

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ