Today we had only five bugs to triage, yet the meeting still lasted a typical half-hour. That sounds familiar.
WiX Online Meeting #84 Highlights
Tuesday, October 6, 2015
Issue triage
-
Bug 4919 | The native version resource of the tools does not match the installer version was opened by our very own Rob, who wanted more resources to have the same version number. Due to Windows Installer limitations around ProductVersion, we need to keep the build number in the third version field. This change is for WiX v4.0, to keep the bundle and binaries in the same format: major.minor.release.buildnumber.
-
Bug 4918 | Burn ignores DisplayInternalUI=true for MSIs with EmbeddedUI reports yet another problem using
MsiPackage/@DisplayInternalUI. This particular problem is a limitation of Windows Installer, trying to run an embedded UI while Burn is running the package as an external UI handler. In the end, this isn’t something we can work around in Burn. -
Feature 4917 | Files-In-Use checking picks up files that correctly handled by the uninstall reports a problem getting in the new files-in-use feature in WixStdBA files (like services) that won’t be use when they’re actually uninstalled or upgraded. Windows Installer is in charge of providing those files-in-use messages so we opened this as a feature request to support dropping authored files from the files-in-use message.
-
Bug 4892 | .Net 4.5.1 compiler failing was unchanged from last week. We resolved it to keep it off the untriaged queue, but we hope the reporter will come back with the requested data.
-
Bug 4885 | RunOnce is triggered during installation on Windows7 x86 systems was once again in my queue to investigate. I did—really, I swear!—but did not find enough data to make sure the problem is the same as we’ve seen before. So I promised to dig deeper this week and ask the reporter for more data if needed.
WiX v3.10.1
We ran into a small snag implementing last week’s plan to ship a WiX v3.10.1 release candidate: Though the pull requests for the approved fixes were committed, we couldn’t get a build published due to problems with Outercurve’s digital-signing service. Outercurve folks are on the case so we hope to get the build out shortly and stay on track to release on Hallowe’en.