Replies: 3 comments
-
I don't think that's the right way to reference |
Beta Was this translation helpful? Give feedback.
-
@robmen It does look like a logical thing to do. However, if I just write this in my Bundle.wxs, it works: <BootstrapperApplication>
<bal:WixStandardBootstrapperApplication LicenseUrl="https://www.example.com/license" Theme="hyperlinkLicense" />
</BootstrapperApplication> If I however do this in .wixlib <Fragment>
<BootstrapperApplication Id="MyInstaller.BootstrapperApplication">
<bal:WixStandardBootstrapperApplication LicenseUrl="https://www.example.com/license" Theme="hyperlinkLicense" />
</BootstrapperApplication>
</Fragment> and this in Bundle.xml: <BootstrapperApplicationRef Id="MyInstaller.BootstrapperApplication" /> it compiles fine, but just doesn't work, the installer just quits silently. That is why I had the definition above for WiX 4.0 (which did work). However, it doesn't for WiX |
Beta Was this translation helpful? Give feedback.
-
And I see why now. The first creates this in the Burn manifest: <UX PrimaryPayloadId="WixStandardBootstrapperApplication_X86">
<!-- ... -->
<Payload Id="WixStandardBootstrapperApplication_X86"
FilePath="wixstdba.exe"
SourcePath="u3"/>
<!-- ... -->
</UX> While the second creates this: <UX PrimaryPayloadId="MyInstaller.BootstrapperApplication">
<!-- ... -->
<Payload Id="WixStandardBootstrapperApplication_X86"
FilePath="wixstdba.exe"
SourcePath="u3"/>
<!-- ... -->
</UX> And then |
Beta Was this translation helpful? Give feedback.
-
In v4 I used to define a BootstrapperApplication in a wixlib as follows:
And then I used it like this in my Bundle.xml:
Now building the wixlib fails with the error
So the goal (which I had accomplished for v4 and v3) is to have a WixStandardBootstrapperApplication with a customized UI in a wixlib.
Beta Was this translation helpful? Give feedback.
All reactions