IBootstrapperBAFunction is part of Neil's ExtendedBA right?  That's new in 3.8, 
so I would think we could still make breaking changes to it.
 
Sean
 
From: jacob.hoo...@greenheck.com
To: wix-devs@lists.sourceforge.net
Date: Mon, 14 Oct 2013 16:44:41 +0000
Subject: Re: [WiX-devs] Thoughts on a self updating bundle









  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.
 
  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.
 
DECLARE_INTERFACE_IID_(IBootstrapperEngine, IUnknown, 
"6480D616-27A0-44D7-905B-81512C29C2FB") vs interface IBootstrapperBAFunction
 
  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).
 


From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]


Sent: Friday, October 11, 2013 1:33 PM

To: Windows Installer XML toolset developer mailing list

Subject: [WiX-devs] Thoughts on a self updating bundle


 
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                           
          
------------------------------------------------------------------------------
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

Reply via email to