I'm going to assume that you have the binaryref tag in your patch family.
The "pure WiX" patching method has a bug in torch that doesn't update the path
for binary entries in the upgrade path. Nor does melt extract the binary file
for you. You will need to do these things manually at the moment to get the
new CustomAction into the patch.
________________________________________
From: kirannhegde [kirann.he...@gmail.com]
Sent: December 1, 2014 1:15 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Patch sequencing problem - Small update + a supseding
hotfix
Hello All,Here is my scenario:Base product has a version of 1.0-I have a
small update(QFE) which has a sequence number of 1.0.6.0The small update
contains a file named PatchCustomActions.dll with a version of 1.0.3.0Patch
code: {2BA41362-74A7-427D-A219-93CBFF4C5844}The small update also contains a
text file name Sample.txt which has the text : Hotfix 3-I have another minor
upgrade msp package which has a sequence number of 1.0.4.0The minor upgrade
contains the same file named PatchCustomActions.dll with a version of
1.0.0.0Patch code:{7E832DAB-2AD8-440F-A3B5-2558237E53D7}The minor upgrade
also contains the same text file name Sample.txt which has the text :
Hotfix Rollup Pack 1Few other facts about the packages:-Both the small
update and minor upgrade target the base product v1.0.-The minor upgrade
also has the supersedence bit set(i.e it supersedes all preceding hotfixes
which belong to the same family and has a lower sequence number).-The minor
upgrade transforms the product version to 1.1-The small update has a higher
sequence number than the minor upgrade package as i dont want the small
update to be superseded.Scenario:I install small update followed by the
minor upgrade package. The windows installer log states that the logical
order of application of the patches is the small update followed by the
minor upgrade.However, at the end of the installation, i observe that the
version of PatchCustomActions.dll is still 1.0.0.0(i.e the version
contained in the minor upgrade, even though the small update contains
v1.0.3.0 of the dll).Could someone explain to me as to why this is
happening?Attached is the log file for your reference.Any help woudl be very
much appreciated.Thanks,Kiran Hegde HRP1_+_HF3.log
<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7598304/HRP1_%2B_HF3.log>
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-sequencing-problem-Small-update-a-supseding-hotfix-tp7598304.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
