This week's meeting had more on the agenda than usual, so this week's meeting highlights have more to cover than usual.
WiX v3.10.3 update
This week's update on WiX v3.10.3 is that there will be a branch for WiX v3.10.3 and the existing fix from @jchoover will be cherry-picked into the branch. And so will the workaround/fix/whatever it ends up being for the GDI+ bug—when we have it. As of today, we don't; there's a Connect bug on the WinForms side of the GDI+ failure and the WinForms folks are following up.
Issue triage
Web Documentation for WixNetFxExtension is mangled #5210 is a report from @NameOfTheDragon that one (or maybe more than one) page on the WiX Toolset web site isn't building correctly. We created a new milestone—creatively named
Web—for issues like this that affect the Web site rather than a particular release of the WiX Toolset.LuxLib.wixproj : error : Unrecognized Guid format #5212 comes from @jasper22 and reports a problem building the WiX v4.0 version of the Lux extension's .wixlib. The official WiX build is from MSBuild projects, not Visual Studio solutions, so we recommended that to the reporter. Still, the project should load and build successfully, so we took this bug in WiX v4.0.
light.exe returns -2146232576 in Windows 2016 Docker container #5213 is from @eerhardt, who's trying to build the .NET Core command-line tools installer (contributed by our very own @robmen) in a container on the still-in-technical-preview Windows Server 2016. Eric and I went back and forth a few times on things to try to diagnose the problem but didn't make a lot of progress. As WiX works as expected outside a container, I'm leaning toward this being a problem with all the beta bits of containers and Eric's engaging people inside Microsoft for their help. We'll leave this issue open and untriaged for a while to see what happens.
WiX 3.11.0.129 doesn't work with Visual Studio 2015 #5214 is a report from @HB-2012 stating that Votive v3.11 doesn't load in Visual Studio. Sad, but true—something I discovered during my own testing and fixed a couple of weeks ago. As @rseanhall notes, the fix will appear in the next WiX v3.11 build.
4.0 Duplicate Symbol error when referencing WixUI_Minimal #5216, from @seannerd, reports a problem using WixUI in WiX v4.0. We took the bug in WiX v4.0.
Pull request and issue templates
This was my agenda item: To talk about how (or if) WiX should adopt the new GitHub feature that allows projects to have templates for new issues and pull requests. I recently added a file that shows up as a link when someone creates a new issue. But it requires a second hop to see; the template would be part of the issue itself and the user would have to explicitly ignore or delete it if they didn't want to follow it. Our goal is to streamline the process of reporting a bug or requesting a new feature: Often we need a couple rounds of "what did you mean?" or "our bloodlust for logs is not yet sated!" before there's an actionable issue. We hope a template would help with that.
Discussion was fairly noncontroversial. We decided to create a template based on our current CONTRIBUTING.md for issues. We also decided that we didn't see much value in a template for pull requests.
I took the action item to create the template. (And I can't believe I just said "action item.")
Pull request review
This week's pull request comes from yours truly and partially implements a feature request for Burn to write all the registry values that the Windows App Certification Kit expects to find. It's a partial implementation because we don't have a concept in Burn bundles of a single "installation directory."
.NET Foundation
Rob reported that because of issues with assignment agreements (among other reasons), it's time to the WiX Toolset from the Outercurve Foundation to the .NET Foundation. There's no strict timeline but the process is underway. There should be no change to consumers of WiX and only minor (and generally positive) change to contributors to WiX. More information to come.