Today we did something we haven't done in a while: We had a short meeting. There were only a few issues to triage and none of them were controversial -- which, it turns out, is the most common reason we turn a small number of issues into a long meeting.
WiX v4.0.2
Remember when we said that:
WiX v4.0.2 will instead ship before our next meeting in two weeks, specifically by shipping it one week, on 12-Sep.
That statement turned out to be almost entirely accurate, which as far as software estimates go is amazing. WiX v4.0.2 did indeed ship before our next meeting (this one). But we were a day off, due to some last-minute wrangling of Authenticode signing infrastructure. Instead, WiX v4.0.2 shipped on lucky 13-Sep. For details, take a look at our blog post and the WiX release notes.
Issue triage
WIP: WiX v5: Default major upgrade behavior and localized error message, from @barnson, remains on the agenda for a future meeting but there was interesting discussion about the Virtual Symbol Feature™ and Rob targeted next week for his spike (in the Scrum sense of researching and learning) that he might do on a livestream. If so, tune in for WiX internals fun!
build -outputType is ignored, from @robmen, reports the sadness that the
-outputTypeswitch that lets you override the default output type that WiX sets based on an output file's extension doesn't work. Most people didn't notice but it's an important enough bug that Rob slipped it into WiX v4.0.2.Evaluate potential for good error messages when mixing WiX extensions between v4 and v5, from @barnson, came from a discussion we had at last week's meeting about what happens when you try to use a WiX v4 extension with WiX v5 (and vice versa). Rob took the issue to try to get good messages instead of, say, crashes.
System.ArgumentNullException, from @jhjacobs, reports a crash (:sad_face_emoji:) with a particular set of bundle payload authoring. There's some gnarly code paths due to the variety of ways you can author payloads but Rob bravely volunteered to wade into the gnarly and emerge with an error message.