WiX Online Meeting 306 Highlights

WiX v7 was released on schedule and we're enjoying spring weather with occasional April showers bringing May WiX v8 features. Or later, because our next milestone is WiX v8.0.0-rc.1 in ten months. Pick up WiX v7 and get your bug reports and feature requests in, because 2027 will be here before you know it.

WiX v7 checkin

WiX v7.0.0 was released on schedule on 6-April. Read the announcement blog post. On to WiX v8!

Issue triage

Cleaning project doesn’t clean publish folders, from @DoctorKrolic, suggests that a project reference that is published isn’t cleaned when the .wixproj is cleaned. It’s not clear the MSBuild magic is in place for that but Rob volunteered to take a look.
Localized resources for WixStandardBootstrapperApplication reference .NET framework as a prerequisite, although that is a non-managed C++ application, from @bobhairgrove, points out localization strings used for the “pre-req” BA mention .NET Framework (which made sense back in the day, but is less likely to be the case these days). Unfortunately, we’re installation and servicing experts more than translation experts, so this issue is up for grabs for those with a soupçon of parole extranjeros.
Configurable-scope bundles should not fail on related bundle built with v6 or earlier, from @barnson, is a bug that came from working with a FireGiant customer getting in on the ground floor for the support for configurable-scope bundles in WiX v7. That bug was fixed in WiX v7.0.0.
OnCacheAcquireResolving’s wzDownloadUrl argument is always null, from @barnson, reports a bit of missing information from one of the callbacks bootstrapper applications get. With a one-line fix, the information is no longer missing. This fix made it into WiX v7.0.0.
Warn about an already signed file, when ‘wix detach’ is called to extract the engine, from @twoelfer, requests a bit of extra information that would help diagnose signing problems. As signing problems, especially on a CI/CD build system, are the problems most likely to cause premature aging and/or table flipping, every bit of extra help is a good thing, and this issue is up for grabs.
“DELETE” key stops working, from @mguma, shouldn’t actually be here—FireGiant tracks HeatWave issues over in their GitHub discussions. But we kept it open to report that it was indeed a HeatWave bug and has been fixed in the release of HeatWave v1.0.8, available now from Visual Studio Marketplace or wait for a notification inside Visual Studio.