We had a few more issues than normal, as we missed our last fortnightly meeting due to an attack of Flumaggedon that took down Rob. (Then I was briefly sidelined as well but as I'm over 2000 miles away from Rob, I probably can't blame him for sharing.)
Issue triage
Request for an --ignore flag to the WiX installer to ignore absence of .NET 3.5, from @tsirakisn, requests the ability to skip the check for .NET 3.5 in the WiX installer. As WiX v3.14 and v4.0 drop MSBuild support for .NET 2.0, they also skip the prerequisite check.
Error MSB4057: The target "_IsProjectRestoreSupported" does not exist, from @armsee, is an MSBuild issue due to WiX v3's use of all-custom targets. As WiX v4 uses the MSBuild common targets, it doesn't suffer from this issue.
Preprocessor documentation is lacking, from @PerMildner, reports a number of issues with the documentation on WiX's preprocessor, in enough detail that, frankly, a pull request might have been easier. Nonetheless, the issue is open for someone to take on.
Installing a bundle package on remote machine, from @nirbar, suggests that Burn could become a remote installation engine. While intriguing, we agreed Burn is the wrong layer to do that.
RemoveRegistryValue documentation implies it can appear inside a RegistryKey element, from @jdh28, points out what might possibly be a bit of overzealous copying and pasting in the WiX documentation. We opened the issue for fixing any time.
Torch.exe fails to complete on RS3+ OS due to new feature associated with temporary files creation, from @Manishd79, reports a problem running Torch. Details were light but as the problem stems from the use of the very old
TempFileCollectionclass, WiX v4 won't suffer from this problem as it doesn't use this class.WiX Visual Studio Extension Icons, from @walker1637, requests updated icons in Votive. As none of the core WiX contributors moonlight as graphic designers, we're going to need more creative volunteers on this issue.