The defense,– option has been added, which can be used to indicate the path to a file that becomes a license.txt file. This does not apply to the license displayed during installation, but it is an easy implementation for addressing the installation license file. The file contains text (a whole license!), and the text is reasonably formatted. stackoverflow.com/questions/16978501/how-to-create-a-bootstrapper-application-without-a-license-agreement-step ExitDlg is the dialog box in the built-in WixUI dialog boxes that is displayed at the end of a successful setup. ExitDlg supports the display of customizable optional text and an optional box. If z.B. the license field for the package section is set to GPL-3.0, the GPL-3.0 license must be generated automatically in RTF format. Custom licenses require a manual modification of the WiX Source (wxs) file, but licenses supported by the license field must be automatic. There are many license ids supported, so that perhaps only first support the most common used by the Rust project: Apache-2.0, MIT, and GPL-3.0.
You can customize some visual aspects of the interface by simply providing replacement files. You can create standard bitmaps, symbols and license texts, but you can create your own bitmaps, symbols and license text. You can also replace selected files, not all of them. Your paths are stored in variables that you can specify either in the command line or directly in the source code: WixUIExtension.dll contains a default license agreement. To specify your product`s license, crush the default setting by specifying a WiX variable called WixUILicenseRtf with the value of an RTF file containing your license text. You can set the variable in your WiX creation: There is a well-known problem with the rich text control that is used to display the text of the license file, which can lead to displaying the empty text until the user scrolls down into the control. This is usually caused by complex RTF content (z.B the RTF generated when recording an RTF file in Microsoft Word). When you run this behavior in your installation user interface, one of the following problems bypasses is corrected in most cases: I tried the code below with the UI-CustomDialog.wxs file, but it didn`t work. It shows the stage of the EULA. The WixUI dialogue library contains standard bitmaps for the context of the home and closing dialogues as well as the top banner of the other dialog boxes. You can replace these bitmaps with their own product brand purposes. To replace standard bitmaps, specify WiX variable values with the file names of your bitmaps, just like when replacing the default license text.
If the License File field is used in the manfiest package, it is used for the license file.rtf, but I`m not sure how the file will automatically be converted to RTF.