Today's meeting happened as it would have normally been scheduled but because the wix-devs mailing list was down, not many people knew about it. Still, we had a quorum and triaged a handful of bugs.
WiX Online Meeting #74 Highlights
Wednesday, July 22, 2015
New/old issue triage
-
Bug 2246 | heat throws ArgumentNullException was re-un-triaged (if that’s a word) with details about current behavior of the bug. We kept it open as a candidate to fix in v3.x.
-
Feature 4821 | Add preprocessor variable with WiX version came back with additional detail that convinced us (well, most of us, anyway) that there are interesting scenarios that are difficult to accomplish otherwise. So it’s now open in v3.x.
-
Feature 4826 | Support Windows Server Core without WoW64 support is a feature request to support machines that don’t have the WOW64 32-bit layer on 64-bit Windows. (It’s possible on Windows Server to remove 32-bit app support, though it’s not commonly used as so many apps are only provided in 32-bit versions.) For WiX, this means providing 64-bit custom actions and Burn engine. It would be possible to additively support a full set of 64-bit custom actions in WiX v3.x. Today, the 32-bit Burn engine is used for both x86 and x64 platforms, so a 64-bit Burn engine would be v4.0-only.
-
Feature 4827 | WIX_ACCOUNT_ADMINISTRATORS does not work as expected when trying add user to local Administrators group says that using the WIX_ACCOUNT_ADMINISTRATORS custom action property fails when that’s used as a parent group for a new user. Apparently, the fully-qualified group name can’t be used. We opened this feature request in v3.x as it would require adding a new property.