[wix-users] Questions regarding msp generated using pure WIX
egcastr at gmail.com
Fri Aug 24 22:51:30 PDT 2018
I don't know about issue #1 but for issue #2 I can say that if you change
the baseline, then those patches will only have changes since that new
baseline. If you want your patches to include all changes since the
original release, then you must keep your baseline as the original release.
Edwin G. Castro
On Fri, Aug 24, 2018 at 9:29 PM manish duggal via wix-users <
wix-users at lists.wixtoolset.org> wrote:
> Hello Experts
> I am struggling with couple of issues when generating patch using pure
> WIX. Appreciate your help to resolve those
> Issue # 1: Supersede logic for the patches
> I have a simple patch.wxs with details as
> <Patch AllowRemoval="yes"
> Manufacturer="$(var.Manufacturer)" DisplayName="$(var.DisplayName)
> (KB$(var.KBArticle))" Description="$(var.Description)"
> Classification="$(var.Classification)" MinorUpdateTargetRTM="yes"
> MoreInfoURL="$(var.MoreInfoUrl)$(var.KBArticle)" Comments="KB
> <!-- Media Element Documentation Reference
> Id: Numeric value >= 1. Represent DiskId for Media with MSI/MSP source.
> Cabinet: Name of the cab file to hold files --> <Media
> Id="1" Cabinet="GAPlus.cab"> <!--
> PatchBaseline details, used for patch applicability Id: value
> is used while creating Patch (Pyro) Validate: Comparison to
> perform when validating update applicability.
> ProductVersionOperator: Installed ProductVersion <= Upgrade ProductVersion
> i.e. Patch is applicable only if installed version is lesser than Upgrade
> version Comparison is for Major.Minor value only -->
> <PatchBaseline Id="GAPlus"> <Validate
> ProductVersionOperator="LesserOrEqual" ProductVersion="Minor"/>
> </PatchBaseline> </Media>
> <!-- PatchFamilyRef Element Documentation Reference
> --> <PatchFamilyRef Id="AgentUpdate"/> </Patch> <!--
> Fragement Element Documentation Reference
> --> <Fragment> <PatchFamily Id="AgentUpdate"
> Version="$(var.ProductVersion)" Supersede="yes"/> </Fragment>
> I am increasing the ProductVersion value with every build. So first MSP is
> 1.1.0, next is 1.2.0, next is 1.3.0 and so on. However, if I deploy 1.3.0
> patch and later try to deploy 1.1.0 patch - it let the override so it leads
> to downgrade. Could someone please help me understand what am I doing wrong
> Issue # 2 - Patch to cater multiple MSIWe plan to release the MSI every 3
> months for same "Product Code". After every MSI release, we change the
> baseline to the most recent released MSI and then generates patch using
> this baseline. We want the patches to be applicable to all released MSI(s).
> What detail needs to be included in my patch.wxs for this purpose? Does
> anyone have an example / sample WXS and commands info to support this kind
> of scenario?
> Thanks in advance for your help!
> WiX Toolset Users Mailing List provided by FireGiant
More information about the wix-users