WiX v3.11 continues its march toward the finish line. We've had more than 10,000 installs of the WiX build tools and even more of the WiX Visual Studio extensions.
WiX Online Meeting #126 Highlights
Tuesday, April 25, 2017
WiX v3.11 status
There are a few remaining v3.11 open bugs, which Rob has promised to knock out this week. We remain on track to ship the final build of WiX v3.11 on 5-May.
Issue triage
-
WiX installer repairs prerequisite .NET package, from @dvorn, points out that there’s code in the WiX bundle’s bootstrapper application to skip repairing .NET that’s never triggered. The fix is easy and @dvorn provided a pull request that we’ll take in WiX v3.14.
-
TypeLib cannot be repeated for both 32-bit and 64-bit components, from @mikekaganski, shows a deficiency in how registry ids are calculated. Specifically, the bitness of the component (whether it’s 32-bit or 64-bit) isn’t taken into account, so registry values can end up with duplicate ids, breaking the build. Unfortunately, a fix would break patching, so it can only happen in WiX v4.0.
-
CustomAction fails - Cabinet error code 1, from @gslysz, reports a problem with managed-code custom actions on Windows 10. We took the issue into WiX v4.x for someone to investigate.
-
Burn should allow BA to provide update feed source, from @barnson, requests the ability for a bootstrapper application to change the source for a bundle’s update feed. Today, it’s a string that’s hard-coded in bundle authoring and it cannot be changed, even if a BA really, really wants to. That’s a shame, so we took the issue into WiX v4.x for investigation.