Closed Antelope-IT closed 2 weeks ago
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.
This issue was closed because it has been stalled for 30 days with no activity.
Unlike the NSIS target there doesn't appear to be an easy way to customise or brand the MSI installer. The NSIS configuration provides the following properties;
installerSidebar
andinstallerHeader
to customise the visual aspects of the installer andinclude
to add custom actions via macros. From the Wix documentation it should be possible to customise the installer UI by passing the following arguments to the Light executable-dWixUIBannerBmp=<SomeBitmapFile 493 x 58>.bmp
for the top banner and-dWixUIDialogBmp=<SomeBitmapFile 493 x 312>.bmp
In addition Light will need to know which directory to search for these two files and its suggested that this can be provided with the argument-b <Path>
.The electron-builder MSI Configuration documentation states that there is the property
additionalLightArgs
for just this purpose. However, if you attempt to use this property you get the following error:The property
additionalLightArgs
is unknown. The documentation needs updating?That leaves the other Wix related configuration property
additionalWixArgs
If you pass the same 3 values ("-dWixUIBannerBmp=<SomeBitmapFile 493 x 58>.bmp
", "-dWixUIDialogBmp=<SomeBitmapFile 493 x 312>.bmp
", "-b <Path>
") toadditionalWixArgs
then with the "-b <Path>
" value the build fails with an error that "-b <Path>
" is not a valid argument for Candle.exe, If you remove "-b <Path>
" from the list of values then you get an errorLight seems to understand the args but can't find the files.
If you pass absolute file paths then the build just freezes - the process has to be terminated. If you pass relative paths such as you can with NSIS then again you get file not found errors.
A minimum requirement would just be some up-to-date documentation that explains how to make this work with the existing configuration properties to achieve the same results as we can for NSIS targets.
Ideally it would more convenient if the MSI configuration had the same respective properties as the NSIS configuration in terms of equivalent poperties to
installerSidebar
andinstallerHeader
and the mechanics of passing the values was handled by the code as it is with the NSIS target.