Today was the Ten Dozenth online meeting! (Rob seemed to like the roundness of 120, so I thought I'd respect that, even though I prefer powers of two. Or hex.)
Issue triage
Burn detects per-machine packages as per-user, when run as LocalSystem, from @barnson, came from an interesting debugging session, where I discovered that MSI treats per-machine packages as "owned" by the LocalSystem account. It makes sense when you think about it and you can even see it in MSI logging (e.g.,
Product {GUID} is admin assigned: LocalSystem owns the publish key.) Luckily, there are no behavior problems in Burn because of this twist but it does result in bad data in the bundle log. We took the issue into WiX v4.0.WiX Heat tool fails on harvesting selfreg data for out-of-process COM servers with CLR Support enabled, from @TigerGalo, reports a particular problem when an .exe is compiled with CLR support. However, Heat.exe has never supported harvesting out-of-proc COM registration, so this is a duplicate to a very old feature request.
WixUI_Advanced presents a UAC prompt for perUser install, from @mattpalermo, is a feature request for the WixUI_Advanced dialog set to support dual-mode packages. WixUI_Advanced was created well before dual-mode packages, so needs to be taught how they work. We took this issue into WiX v4.x if someone likes retro MSI UI and wants to do the work to support dual-mode packages.
Creating a signed bundle is identified as threat by Trend Micro Antivirus, from @miracle152004, confused the assembled team because we couldn't figure out if it reported a built-time problem or an install-time problem. We asked for clarification.
Wixtoolset wix-users/devs forum marking posts forwarded from wixtoolset email server as fishing, from @phillHgl, reports that messages from the WiX mailing lists are being reported as potential phishing attempts. Remember, only give your credit card information when I request it. Rob took the issue to ping the mailing list provider.
WiX v3.11 issue review
We spent a good bit of time reviewing all the open issues in the WiX v3.11 milestone. We winnowed a couple but kept most of them and assured each one had a "willing" assignee. There are 24 mostly small issues that we want to fix before shipping WiX v3.11, including big-ticket items like support for Visual Studio 2017. Keep an eye out for issue updates and feel free to help the friendly volunteers doing the work to keep WiX flowing!