Luckily, last week's rate of incoming issues didn't continue. But we still ended up with 15 issues to triage today.
Issue triage
Bug 4915 | ServiceControl Wait not working in Windows 8.1 reports a problem with
ServiceControlbut as it's Windows Installer, not WiX, that's in charge ofServiceControl, we closed this bug.Feature 4914 | Allow BA to change bundle registration to per-machine is a feature request stemming from a thread on the wix-users mailing list. Per-user/per-machine switching has never worked well—Windows Installer didn't officially support it until MSI v5.0 and then with significant limitations—and Burn doesn't support it today.
Feature 4913 | Burn should update ARP DisplayName during modify is a feature request I opened when I figured out that modifying the
WixBundleNamevariable doesn't cause Burn to update its entry in Add/Remove Programs (also known as Programs & Features, but it'll always be ARP to me).Bug 4912 | Cannot bind transforms without files is another bug in the current pre-beta WiX v4.0.
Bug 4911 | Torch yields error when trying to load wixpdbs is a bug in the current pre-beta WiX v4.0.
Bug 4910 | XmlGetAttribute returns S_FALSE, not E_NOTFOUND is the bug we took today in WiX v4.x to eradicate S_FALSE HRESULT returns from the DUtil native library.
Feature 4909 | Package DUtil up into a nuget package supporting native projects is a feature request with a pull request already pending. We took the issue for WiX v4.0.
Bug 4908 | IIS:Certificate installation error on Windows XP SP3 is another issue of crashing custom actions on Windows XP. I took it to verify that my fix for Bug 4902 also fixes this bug.
Feature 4907 | Impossible to add background image through theme file when using wixstdba requests support for a transparent background image in ThmUtil. We opened it in WiX v4.x.
Bug 4906 | Wixstdba does not compensate for borders and/or title bar size when creating the main window requests that ThmUtil (the engine underlying WixStdBA theme support) adjust the theme size based on the window "chrome." We agreed and opened it in WiX v4.x.
Bug 4902 | MSI built with 3.10 fails to install on XP is the crash bug I took last week to investigate. After a fun evening of remote debugging from a Windows XP virtual machine, I discovered enough keywords to lead me to the Connect issue reporting the same error, and, luckily, a workaround. See below for WiX v3.10.1 news.
Bug 4892 | .Net 4.5.1 compiler failing was unchanged from last week. We asked again for more data.
Bug 4885 | RunOnce is triggered during installation on Windows7 x86 systems came back (once again) from last week, all because I failed in my promise to investigate the logs and report back for this week's online meeting. (In my defense, I was busy with other bugs.) I re-promised to investigate for next week.
Bug 4835 | vs2015 installer build fails came back around but as the error being reported is still from a non-WiX task, we referred the reporter to wix-users for support.
Bug 3640 | Burn will use incorrect package if local came back around to discuss the underlying issue. We opened it again though it might require a WIP for design discussion.
WiX v3.10.1
Bugs 4902 and 4908 are crashes of some WiX standard custom actions when running on Windows XP. Crashes are bad—bad enough that we need to issue a maintenance release of WiX v3.10 to fix it. Luckily, the Visual Studio 2015 bug report is an identical match to the problem (and even the assembly code) and the workaround in the bug works in my testing.
The plan we came up with is to do a build of WiX v3.10.1 next week and ask the reporters of the bugs—and everybody else!—to take a look. Then, in accordance with the rule that WiX Releases Happen on Holidays,® we'll release WiX v3.10.1 on Hallowe'en.