Today is the day we'd scheduled to ship WiX v5.0.0-rc.1. That's not going to happen, unfortunately, but in what is probably a coincidence (but maybe isn't?!), 2024 gives us until the 29th to still ship in February.
WiX v5 release plan
Between the fallout of the WiX v4.0.4 and v3.14 security and the unknown-unknowns of Rob's work to bring bootstrapper applications out of the Burn process, we did not hit our scheduled date of today for WiX v5.0.0-rc.1. :sad_face_emoji: However, Rob's seeing the end of the tunnel (and it's not an oncoming train) and we're both confident that our unit tests and runtime tests are good enough to keep our confidence high in our work in WiX v5. So we're now slipping day-for-day and hope to have WiX v5.0.0-rc.1 "real soon now." The dates are now:
- v5.0.0-rc.1 on ???-Feb-2024
- v5.0.0-rc.2 on 26-Mar-2024
- v5.0.0 on 5-Apr-2024
Issue triage
Page Not Found: v3.14.0.4118, from @aquacode, reported that a very old development build of WiX v3.14 was no longer available. Yep, that's what happens to development builds: they go away and you should upgrade to later development (or release) builds -- especially when older builds have a known vulnerability.
WiX v5 should(?) reject v4 extension Nupkegs, from @barnson, is a duplicate of another bug I opened, just with different wording. It's apparently how my brain decided to try to get me to implement a fix. Mission accomplished, brain.
wix.exe : error WIX0001: System.ArgumentNullException: Value cannot be null. (Parameter 'value'), from @a-coda, reports what is likely a simple bug in the MSI package decompiler, so I volunteered to fix it in WiX v5.
HKMU-RegistryKey not removed after parallel per-user and per-machine install/uninstall, from @lilagerd, reports "interesting" behavior from MSI when mixing per-user and per-machine packages. The behavior is consistent with a typical component rules violation so we're confident that MSI just didn't contemplate the same package being installed simultaneously in both per-user and per-machine contexts.