Today was 2016's final WiX Online Meeting and, as appropriate for a time of year when many people use up their vacation days, we had a small crowd and quickly finished up triage so we could indulge in panicked last-minute shopping and nog-based beverages.
Error 0x80070057: WriteIIS7ConfigChanges Failed when setting WebAppPool identity., from @TheCycoONE, reports a failure in WixIIsExtension when specifying a custom user for an app pool. As IIS itself doesn't give much useful feedback on such errors, someone will need to debug the custom action code to see what's going on. We opened the bug in WiX v3.x.
Embedding multiple CAB Files => E_FAIL, from @punkbuster2003, reports a problem building a big MSI package when using files from binary .wixlibs. We took this bug in WiX v4 to investigate the root cause.
Project outputs from .wixproj are not available to other projects, from @heaths, reports on some typical MSBuild project functionality that isn't implemented in the WiX v3.x MSBuild targets. We closed this issue because the WiX v4.0 MSBuild targets use the common MSBuild targets and implement the desired functionality.
wixproj ItemGroup entries with env vars will not load in VS2015, from @babzog, demonstrates a limitation in Votive's use of the Managed Package Framework for Projects code. We opened this bug in WiX v4.x to investigate upgrading to a later version of MPFProj that supports environment variables in items.
Performance Counters - Multi-instance or average based counters are not created properly with heat, from @sjswoboda, that Heat's support for harvesting performance counters—who knew Heat could do that?—fails on multi-instance performance counters. @sjswoboda also provided a pull request to fix the bug in WiX v3.x. We asked for a pull request in WiX v4.0 to keep it up to date so hopefully we'll get the fix in both repos.