I don’t think that is correct, you base your class on IBootstrapperBAFunction
and then only implement the functions you want.
Neil
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: 15 October 2013 15:23
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] Thoughts on a self updating bundle
The one thing I didn’t see was a true framework BA function base class. If we
have one that just implemented the default behavior for each function, assuming
anyone who writes their own BA function inherits from it , they would then not
have to change anything to get the updated code to compile. As is today, they
would need to implement any new interface members in order to be able to
compile.
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, October 14, 2013 11:48 PM
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] Thoughts on a self updating bundle
Note: we can *add* methods to existing interfaces from backwards compatible
version to version. We do not try to maintain binary compatibility with WiX
toolset releases. In other words, if someone takes a new drop, they are
expected to rebuild all of their stuff against the new drop.
Now, when they recompile against a backwards compatible release everything
should just build and work. If not, then we should fix that as quickly as
possible.
On Mon, Oct 14, 2013 at 8:28 PM, Bob Arnson
<b...@joyofsetup.com<mailto:b...@joyofsetup.com>> wrote:
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.
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.
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.
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<mailto:WiX-devs@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
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
