Hmm, what does your detect sequence look like in your MBA?
Did you implement
OnDetectUpdateBegin, OnDetectUpdate, OnDetectUpdateComplete?
In OnDetectUpdateBegin are you:
Returning a recommendation of IDOK (not certain of the managed
equivalence of this is)?
In OnDetectUpdate, are you (if you found an update):
Calling Engine->SetUpdate
Setting the launch action to UpdateReplace?
Returning a recommendation of IDOK?
-----Original Message-----
From: Phill Hogland [mailto:[email protected]]
Sent: Thursday, July 10, 2014 2:51 PM
To: [email protected]
Subject: [WiX-users] 3.9.702 Bundle update behavior
I upgraded from 3.8.1128 to 3.9.702 a few days ago, and I am observing a change
in behavior in the why my bundles are updated. (I am aware that there are new
features in 3.9 related to bundle updating, but was not expecting this behavior
change. At the same time I did not revert my build system back to 3.8 and
validate that this observation is related to upgrading the wix tools.)
Previously I would create a new build of my bundle and post the build to my web
host site, with the external packages, and an atom feed file, similar to the
implementation in the Wix toolset setup. IF the user ran an older build, the
mba/engine checks the atom feed url, and if a newer build is detected the
'Update Available' button is presented. The user clicks the button and the
remote bundle is downloaded and started moving from say build
1.0.5 to 1.0.10 (even if previously I had launched 1.0.5 and installed an then
uninstalled 1.0.7 prior to creating the 1.0.10 build). Also the bundle seemed
to be cached in a folder under c:\ProgramData.
Now when the user runs 1.0.5 (with no packages cached in ProgramData, or the
local setup folder), 'Update Available' is presented and when clicked, the
bundle then runs 1.0.6 and presents 'Update Available' again. The user clicks
and it runs 1.0.7 and presents 'Update Available' again, etc marching
up to the latest which it finally downloads from the web site. It seems to
have ached these files under the user's ..\AppData\Local\Package Cache\.
So is this the expected desired behavior to present the older bundles first
before getting the build that I posted to the web site?
Is there a code change I can implement (in my mba?) to get back to the behavior
where it gets the latest bundle I posted to the web site?
Thanks. Phill
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/3-9-702-Bundle-update-behavior-tp7595761.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse Turn
processes into business applications with Bonita BPM Community Edition Quickly
connect people, data, and systems into organized workflows Winner of BOSSIE,
CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
