All text displayed in built-in WixUI dialog sets can be replaced with custom strings if necessary. To do this, you must add a string to your product`s WiX location file (WXL) that had the same ID value as the string you want to replace. You can find the Id values of the WixUI string by searching for the WixUI_en-us.wxl file in the WiX source code. Look at the control with the id “LicenseText” and read the comments. We have the original license text source in “$(var. ProjectDir)! (years. LicenseRtf)”. Var. ProjectDir is the directory of the project file. That! (years.
LicenseRtf) is where the magic below is the script of my main WiX file to create the MSI installation package. In this file, I combined the code to add the installer ui, which contains the following custom dialog boxes: There are a few other subtleties, such as a license agreement page: The WixUI dialog library contains standard bitmaps for the background of the Welcome and End dialog boxes and the top banner of the other dialog boxes. You can replace these bitmaps with your own for product branding purposes. To override the default bitmaps, specify the values of the WiX variables with the file names of your bitmaps, as you would when replacing the default license text. But where do these police identifiers come from, you may ask? OK, here they are. A simple and centralized way to specify different text styles and easily reference them from anywhere in the interface. For color, you can use the red, green, and blue attributes (each with a value between 0 and 255) for additional bold, italic, underlined etstrike` decoration: Added the -l,–license option, which can be used to specify the path to a file .txt to the License.txt file. This does not affect the license that appears during installation, but it is a simple implementation to process the license file of the installation location. The final step is to add the LicenseAgreementDialogOverwritten extended license dialog box to the installer GUI string.
So, of course, this is done under the node. Next comes the text of the license agreement. We open a pressed text with scrolling content. The actual text enters the internal text tag. You can use RTF-style text here, so it`s best to create your license agreement in a word processor and export it to RTF format (Wordpad is probably the best word processor for this purpose, the more sophisticated can create much more detailed RTF files; even if you use them, you must register the final version of Wordpad again): If, as part of this implementation, the -l, –license is not used, the license-file field is used in the package manifest (Cargo.toml). . . .
