Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and
10.00.37.0004 (HF2).
I am changing the bundle version as well as the version of the msi, but
still the second patch for the bundle appears alongside the first one, not
replacing it as I would expect.
Do I need to do something to "hide" the first patch when the second one is
applied? And if so, how would I undo this when uninstalling the second
patch?
As these are cumulative, removable patches, only one entry must exist in the
"Installed Updates" of ARP.
I do see where it realized the first patch bundle was installed, but did
nothing with it.
Plan 3 packages, action: Install
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on
package with no dependency providers: Netfx4Full
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on
package with no dependency providers: S3DInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C193CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch.log'
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleRollbackLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C193CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch_rollback.log'
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on
package with no dependency providers: RADInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Planned package: Netfx4Full, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[0F98:0E38][2012-11-14T16:19:55]: Planned package: S3DInstallPatch, state:
Absent, default requested: Present, ba requested: Present, execute: Install,
rollback: Uninstall, cache: Yes, uncache: No, dependency: None
[0F98:0E38][2012-11-14T16:19:55]: Planned package: RADInstallPatch, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
*[0F98:0E38][2012-11-14T16:19:55]: Planned related bundle:
{1ca42db4-c103-4fa2-ba05-d3c20f8f5d70}, type: Dependent, default requested:
None, ba requested: None, execute: None, rollback: None, dependency: None*
Then in the msi install log, I see
Final Patch Application Order:
MSI (s) (44:2C) [16:20:06:348]: {379A67FF-1175-42B8-B7B7-8F8ED98CA7EB} -
C:\ProgramData\Package
Cache\{379A67FF-1175-42B8-B7B7-8F8ED98CA7EB}\S3DInstallPatch
MSI (s) (44:2C) [16:20:06:349]: Other Patches:
*MSI (s) (44:2C) [16:20:06:349]: Superseded:
{ADC561F5-6FC8-4EA1-8DB1-E79A7F18A7DD} - *
Which I can only assume is the First Patch being superseeded, so it looks
like the MSI is correct, just not the Bootstrapper.
Is no one else facing this problem? Or does no one do cumulative patching?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Bootstrapper-Second-Patch-does-not-supersede-first-Patch-tp7581779p7581928.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
