I have an EditBox controls in the options dialog of the native bootstrapper application:
<Editbox Name="MyEditBox" X="221" Y="151" Width="-100" Height="21" TabStop="yes" FontId="3" />
In the bundle.wxs file, I have:
<Variable Name="MyEditBox" bal:Overridable="yes"/>
Under the element for the MSI to which I want to pass the value entered by the user in the EditBox control, I have:
<MsiProperty Name="FIRE" Value="[MyEditBox]"/>
However, the MyEditBox is not being set and FIRE is being passed to the MSI as a null string. The above methodology was based on this: Customising the WiX Burn theme with additional inputs
It seems what the link above mentions doesn't work for EditBoxes. To get around this I have set DisplayInternalUI="yes" for the MSI. However, I would still like to not show the MSI dialogs and instead pass properties through the WiX BA dialog using EditBox controls. In time I will write a managed BA which can make this work, but I need to get this working using the native BA for now. As per his link: http://www.mail-archive.com/[email protected]/msg54024.html it would seem that EditBox control can in fact be used to pass properties to MSIs, but I haven't been able to get this to work. Any insight will be appreciated.
UPDATE: I wrote a custom managed bootstrapper which allowed us to get around this issue. As Rob has mentioned there is an extant feature request to implement this in the default BA.
There is a feature request to allow arbitrary edit boxes to have their data stored into Burn variables. As of today, that feature request has not been implemented, although someone has expressed interest in implementing it.