WiX v3.10.3 update
This week's update on WiX v3.10.3 is that this is the last update on WiX v3.10.3. WiX v3.10.3 was released on 4-July as planned (in plan v12.3.9). You can download WiX v3.10.3 and read more about the release on my blog and Rob's blog.
Issue triage
Feature: Please Digitally Sign Wix Toolset, or provide a possibility to sign the delivered CustomAction dlls before MSI Creation, from @BobSilent, requests that the custom action DLLs embedded in the WiX extension DLLs be signed or at least signable. Windows 10 has support for enterprises to block code from executing when it isn't signed by a particular trusted certificate. WiX bundles are signed by a .NET Foundation certificate but none of the WiX binaries themselves, including the embedded custom action DLLs are signed. I suggested we not sign them as it would allow a malicious actor to use, for example,
WixQuietExec
to callcmd.exe
to launch the nuclear missiles. Unfortunately, that means a bigger change that would allow individual files to be signed as they're consumed as part of the Light.exe binding process. Rob took the bug to investigate options.Light: There should be a better error message than "error LGHT0001: Failed to save resource. Error: 87", from @Farrukhw, requests a better error message when using an unsupported source for a bundle's icon. Supporting extraction of icons from .exes would be great but at the very least, Light.exe shouldn't crash when given an unexpected file format. We took this issue in WiX v4.0.
ConfigureSmbUninstall fails when Description is longer than 72 chars, from @phillHgl, reports an inconsistency in the length limit of a field in the
FileShare
custom action. As it looks like a bug, we took this issue in WiX v3.11 for someone to investigate either widening the field or enforcing the limit.RebootPending Burn variable should include bundle pending reboot, from @barnson, points out that bundles "remember" when they require a reboot and refuse to execute if the reboot hasn't taken place, but that state isn't reflected in the
RebootPending
Burn variable. As there's no easy way for a bootstrapper application to detect that state either, we took the issue into WiX v4.0.BundleEnumRelatedBundle returns provider key which can't be used with BundleGetBundleInfo, from @barnson, reports a bug in the WiX native SDK.
BundleEnumRelatedBundle
returns a bundle's provider key when enumerating related bundles but the only function that lets you get information about a bundle—BundleGetBundleInfo
—requires that you pass a bundle id. By default, a bundle's provider key is its bundle id, but the provider key can be explicitly authored. We took this in WiX v3.11 and [Jacob][https://github.com/jchoover] volunteered to take a look.Advanced button in Polish appears in multiple lines, from @czmi3l, is yet another "UI elements shouldn't be designed with English in mind" bug: This time, a Polish word is longer than fits in a button. We took this in WiX v3.x for someone to use that really neat functionality in .wxl files to resize the button for Polish.
Using Wix Toolset on both VS2008 and VS 2015 at the same time, from @oznetmaster, requests that since we deprecated Visual Studio 2008 three years ago, we support side-by-side installations with WiX v3.8. Unfortunately, it's not a trivial amount of work and likely includes work inside Votive itself to support side-by-side installations. We have no Votive experts hanging around and if we did, we'd rather they work on fixing bugs and bring Votive forward rather than working on legacy versions.
WIX Heat not harvesting a reg file properly - outputting the wrong attribute - 'Directory' instead of 'DirectoryRef', from @sharmade, was a report of a Heat.exe bug that I couldn't reproduce after some back and forth with the reporter. We ended up closing this and requesting the user head to the wix-users mailing list to work with the community to determine if there's a real bug lurking about.
Pull request review
There was no pull request review today. You should go create more pull requests for us to review in the future.