[wix-devs] Update BalExtension's IWindowsInstallerBackendBinderExtension

Sean Hall r.sean.hall at gmail.com
Tue Dec 10 19:02:27 PST 2019

Actually, it looks like I didn't translate this code from v3 correctly.
This should be an IBurnBackendExtension, whose PostBackendBind doesn't even
provide the wixout. Or is there a different interface in the new Bundle
backend that this should be implementing?

I think it would be nice
if IWindowsInstallerBackendBinderExtension.PostBackendBind provided the
WindowsInstallerData as an additional parameter.

On Wed, Dec 11, 2019 at 1:42 PM Bob Arnson <bob at firegiant.com> wrote:

> There's no file to load from -- it's all in memory at that point. 😊
> Probably there should be a WixOutput enum/constants/methods for well-known
> WixOutput content. Maybe a WindowsInstallerData Load overload that takes a
> WixOutput (like Save)? I think I like that better.
> -----Original Message-----
> From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean
> Hall via wix-devs
> Sent: Tuesday, 10 December, 2019 21:23
> To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> Cc: Sean Hall <r.sean.hall at gmail.com>
> Subject: [wix-devs] Update BalExtension's
> IWindowsInstallerBackendBinderExtension
> I'm not sure what's the right way to update
> https://github.com/wixtoolset/Bal.wixext/blob/master/src/wixext/BalWindowsInstallerBackendBinderExtension.cs
> .
> Am I supposed to get the information by calling
> WindowsInstallerData.Load(wixout.Uri.AbsoluteUri, false)?
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant
> http://www.firegiant.com/

More information about the wix-devs mailing list