Rob was out when we would have held our last meeting, so we decided to skip it and accumulated a larger-than-average number of bugs in exchange.
Feature Request - Support adding NuGet packages into WiXProj Projects (MSI project or WiXLib), from @stunney, requests support for acquiring payloads of an installer via NuGet packages. NuGet has intimate knowledge of manage-code project types but not so much for WiX, so we took this issue into WiX v4.x for someone interested in NuGet to propose a solution.
WiX v4 should use the Windows 10 SDK for all native code, from @barnson, is a request to standardize on the latest-installed version of the Windows SDK so we avoid having hard-coded SDK versions or a requirement to install older SDKs that aren't installed by default in Visual Studio 2017. As I opened the issue, I volunteered to make the changes.
CopyFile with no FileId results in broken MSI, from @tcostin, exposed a likely-very-old bug in the WiX compiler that parses the
CopyFileelement. There's a simple workaround so we decided to fix it in WiX v4.0.
Firewall Extension does not handle port or protocol changes across change and repair, from @dyhims, requests new functionality from
WixFirewallExtensionto support updating already-installed firewall rules. We took the issue into the WiX v4.x milestone for someone motivated to enhance firewall support.
Wix4 errors in MSBuild messages aren't 0-padded, from @barnson, is an excellent example of a pedantic bug report, something I'm fiercely proud of. WiX v3 formatted error numbers like "CNDL0130" but WiX v4 currently does not. Pretty sure the rule is that after a decade, you can't change things like this. So I filed the issue and will fix it everywhere so I can sleep again at night.
WiX v4 Crashes Visual Studio During Build (Merge Module), from @iswix-llc, is a bug report on the old
wix4repo, before we refactored and reorganized the code into multiple repos. Merge modules are known to not work yet, so Rob volunteered to hold on to this bug in WiX v4.0.