Does anyone has any other thoughts?
Regards,
Kiran Hegde
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-sequencing-problem-Small-update-a-supseding-hotfix-tp7598304p7598398.html
Sent from the wix-users mailing list archive at Nabble.com.
problem - Small update + a supseding
hotfix
Hello,
Thanks for the response.
I am not using Wix to build my patch.
I am using msimsp to build my patch.
Another follow up question:
Is a superseding hotfix meant to replace everything from supserseded hotfixes
, even if that results in downgrade
The experience speaks for itself (tm)
-Original Message-
From: kirannhegde [mailto:
kirann.hegde@
]
Sent: December-01-14 11:42 PM
To:
wix-users@.sourceforge
Subject: Re: [WiX-users] Patch sequencing problem - Small update + a
supseding hotfix
Hello,
Thanks for the response.
I am
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
Hello,
Thanks for the response.
I am not using Wix to build my patch.
I am using msimsp to build my patch.
Another follow up question:
Is a superseding hotfix meant to replace everything from supserseded
hotfixes , even if that results in downgrade of files?
Regards,
Kiran Hegde
--
View
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
6 matches
Mail list logo