[wix-devs] A quick balextension question

[Blair Murri]

If you are referring to the executable we call a bundle: from the burn section of the code the folder "stub" calls into the code in "engine", which loads whatever UX (called the BA/Bootstrapper Application) has been configured.

If the WixStdBA was configured, that code the engine loads is found in there somewhere (IIRC). If managed code BA is configured, then the mba/mbahost code provides the managed/native transitions, and the WixStdBA provides the UX used for loading any prerequisite packages.

The above folder names apply to the wix3 and wix4 repos. For the new WiX v4 repos, that mapping hasn't changed much (yet)

If the user provides their own BA, then the UX is entirely up to them.

If you are referring to how the bundle exe is assembled, it's pretty much all in the binder

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> on behalf of Sean Farrow via wix-devs <wix-devs at lists.wixtoolset.org>
Sent: Tuesday, February 19, 2019 2:41:22 PM
To: WiX Toolset Developer Mailing List
Cc: Sean Farrow
Subject: [wix-devs] A quick balextension question

Hi,

I was just wondering how/where in the source the executable for a bundle is created?
I'm trying to get to grips with the burn/balextension code so I can understand what is happening from an accessibility standpoint.
Kind regards
Sean.
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/