I just got bit again by a stupid bug on my end with my application
self-updates. What I'd really like to do is write a self-updating feature for
a bundle so I can write it once and have it work for all my applications (and
never have to look back again).
My initial thoughts were to pass the bundle ID across to the MSI, and allow an
application to query for the bundle in the package cache based on the bundle
ID. I'd like to be able to execute the bundle from the cache with an /update
parameter and allow the bundle to extract the BA, pass the parameters to the
BA, and allow the BA to do it's check for updates. I know there would be a
desire to keep the implementation generic, so depending on the user they could
choose how to determine if an update is available (version check via
XML/RSS/reading the IMAGE_FILE_HEADER, etc). I'm most familiar with WixStdBA
and I have little desire of writing a managed BA, but I am looking for comments
on where the best fit for this functionality would be. It looks like it could
it be done as an extension to WixStdBA utilizing Neil's recently introduced
BAFunctions concept.
Looking for any thoughts before I take a swing at this.
Thanks,
Jacob
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
