On 14-Oct-13 12:44, Hoover, Jacob wrote:
After looking into this over the weekend it seems interface IBootstrapperBAFunction only has a small subset of possible "events" defined. If we had OnDetectUpdateBegin in the interface then I think I could configure a BA Function DLL to handle the app specific update checks and utilize the existing SetUpdate call to update the bundle.
Seems reasonable.
It's not a proper COM object. So far, we haven't locked the BA interfaces; for example, v3.7 added callbacks and method parameters.The bigger question I have is around the IBootstrapperBAFunction, which doesn't have a GUID associated with it. I assume adding a method to this interface would be considered a breaking change so it wouldn't be accepted till 4.x, but sure would be nice to be able to version the interfaces.
At first I thought I could work around this without making breaking changes to the interface, but as the Update element is "hidden" inside the Manifest it isn't accessible from a UX (without doing a bunch of voodoo to re-extract it from the bundle exe).
Easy enough to add it to the BA manifest. -- sig://boB http://joyofsetup.com/
------------------------------------------------------------------------------ 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=60135031&iu=/4140/ostg.clktrk
_______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs
