Welcome to the 167th WiX Online Meeting, the first since last Friday's 15-year anniversary of WiX's first open source release in 2004! Rob wrote about WiX's 15th anniversary here at Setup Matters and I did so briefly on my blog as well.
Issue triage
NetFxExtension should support .net 4.8, from @Smurf-IV, requests support for the early-access edition of .NET Framework v4.8. As we expect .NET Framework v4.8 to come out with the next version of Windows 10 this month or next, we took this issue into WiX v3.14 if someone wanted to do the detection and bundle package authoring needed to fully support .NET Framework v4.8.
Custom action VS2017Setup does not detect VS2017 when VS2019 is also installed, from @XomegaNet, reports a problem detecting Visual Studio 2017 when Visual Studio 2019 is installed side-by-side. We pinged @heaths who did the original detection custom action for advice.
ResolveSource not working in Upgrade or Uninstall scenario, from @armsee, reports a potential issue getting a source-resolution message from Windows Installer to a bundle's bootstrapper application. Sean volunteered to investigate.
Burn support for WM_SETTINGSCHANGED to refresh environment variables, from @robmen, requests that the Burn engine should refresh its environment variables, to handle the case where one package in the chain wants to update environment variables for a later package in the chain. We took this issue into WiX v4.x should someone be interested in implementing it.
Heat fails to suppress VB6 registry entries when -svb6 is combined with -scom, from @t-johnson, reports that some Visual Basic 6.0 registry values aren't being excluded from Heat harvesting. The reporter also pointed to a workaround they'd made in the Heat code, so we suggested sending a pull request for WiX v4.
Votive v1
Rob did the enjoyable work of getting signed Votive packages building and investigating how to make the Votive templates show up neatly in the new Visual Studio 2019 new-project experience. As soon as those templates look pretty, the plan is to make a release candidate build available for everyone to have an opportunity to kick tires. If the tires are kicked successfully, then it would get promoted to live on the Visual Studio Marketplace. Look for an announcement here and on the WiX-users mailing list. Thanks to @chrpai and @heaths for their help.