If you are using Torch and Pyro (with the Patch element) instead of the
PatchCreation element, you run torch additional times to create the
transforms from each target to the Updated build and pass each of the wixmst
files separately to pyro.

The concept is the same: the patch contains multiple transforms, one set for
each "target". The size of the MSP file, of course, increases nearly
linearly with each additional base you target.

-----Original Message-----
From: Tony Juricic [mailto:tjuri...@tradestation.com] 
Sent: Tuesday, June 01, 2010 1:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patching Base Versions

Here is one example where you can try insert additional targets (bases)

<?xml version="1.0" encoding="utf-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";>


  <?include VersionDefinitions.wxi ?>
  <?include PatchCreationDefinitions.wxi ?>

  <!-- patch id needs to be updated -->
  <PatchCreation Id="{codes}"
                 AllowMajorVersionMismatches="no"
                 AllowProductCodeMismatches="no"
                 CleanWorkingFolder="yes" 
                 WholeFilesOnly="no"
                 Codepage="1252" >
 
  <PatchInformation Description="Product $(var.MAJORMINORVERSION) Update"
                 Keywords="Installer Update Hotfix Patch"
                 Comments="Patches Product $(var.MAJORMINORVERSION)"
                 Manufacturer="My Co"
                 Languages="1033"
                 Compressed="yes"
                 SummaryCodepage="1252" 
                 AdminImage="yes"/>

  <PatchMetadata Description="Product $(var.MAJORMINORVERSION) (Update
$(var.THISBUILD))"
                 DisplayName="Product $(var.MAJORMINORVERSION) (Update
$(var.THISBUILD))" 
                 TargetProductName="Product $(var.MAJORMINORVERSION)"
                 ManufacturerName="My Co"
                 MoreInfoURL="http://www.myco.com";
                 Classification="$(var.CLASSIFICATION)" 
                 AllowRemoval="yes"
                 OptimizedInstallMode="yes" />

    <Family Name="$(var.FAMILYID)" DiskId="2"
MediaSrcProp="PATCH$(var.THISBUILD)" SequenceStart="$(var.SEQSTART)"  >
      <UpgradeImage  Id="Patch$(var.CURQFEID)"
SourceFile="$(var.CURQFEPATH)\myupgrade.msi" >
        <TargetImage Id="PatchRTM" Order="1" IgnoreMissingFiles="no"
SourceFile="$(var.RTMPATH)\mytarget.msi" />
      <!-- add new targets here -->
      </UpgradeImage>
  </Family >

  <TargetProductCode Id="$(var.PRODUCTCODE)" />

    <PatchSequence PatchFamily="$(var.FAMILYNAME)"
                   Sequence="$(var.SEQUENCE)" />
    
  </PatchCreation>
</Wix>


-----Original Message-----
From: XorPtr [mailto:reaper4...@gmail.com] 
Sent: Tuesday, June 01, 2010 4:22 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patching Base Versions



I had a question about whether a feature is supported and haven't seen any
WiX documentation that really answers my question.  Basically I was curious
as to how patches could be installed and supersede each other based on the
base used to create the patch.

For example if I have Product v1.0.3 directly.
I can create a patch for Product v1.0.3 using it as a base and patching to
Product v1.0.4.

My question is, would I be able to install a patch created using the base
Product v1.0.1 which patches to Product v1.0.4, and successfully install it
on Product v1.0.3.  Currently this is effort is failing with a message
saying the program to be upgraded may be missing or the upgrade patch may
update a different version of the program.  

I'm not sure if this is because I have a problem with the patch or if this
just isn't supported by WiX.  If this is supported by WiX, what would be the
best way to go about doing it?

Thanks in advance,

Big Jim.
-- 
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-Base-
Versions-tp5127849p5127849.html
Sent from the wix-users mailing list archive at Nabble.com.



TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS:
TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member
NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading
software and subscription company, and TradeStation Europe Limited, a United
Kingdom, FSA-authorized introducing brokerage firm. None of these companies
provides trading or investment advice, recommendations or endorsements of
any kind. The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or other use
of, or taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.

----------------------------------------------------------------------------
--

_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------

_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to