Today we had seven bugs to triage, and in a change from recent weeks, all were new and none were carryovers from previous meetings.
WiX Online Meeting #88 Highlights
Friday, November 6, 2015
Issue triage
-
Feature 4940 | Add option to harvest dependencies is a request in Heat to harvest the dependencies that are part of a project’s output. We concluded that was a feature we could take in WiX v3.x if it were opt-in with an additional Heat.exe switch. In WiX v4.0, we could take it as the new default Heat behavior.
-
Bug 4943 | bootstrapper UpdateReplace with perUser InstallScope updates incorrectly reports a problem with per-user bundles and bundle updates. Jacob posted about a bug he fixed around per-user bundles and we asked for a bundle log to try to understand the issue better.
-
Bug 4944 | Fail to build Visual Studio 2015 community Windows 10 VM reported a problem building with WiX on Windows 10. The WiX MSBuild tasks currently require .NET 3.5, which isn’t installed by default on Windows 10. We kept the bug open in WiX v3.x to fix the warning that should already be present in the WiX installer.
-
Bug 4945 | VS2015_IDE_VC_PROJECTSYSTEM_INSTALLED property is set when not expected points out that the VS2015_IDE_VC_PROJECTSYSTEM_INSTALLED property is set even when the (now optional) Visual C++ components aren’t installed. We opened the bug in WiX v3.x to investigate what would be required to find the optional components.
-
Bug 4946 | Documentation bug is an issue in the WiX Tutorial that FireGiant maintains. I was happy to file a bug against those fine folks at FireGiant instead.
-
Feature 4947 | Please document that ProductSearch cannot be used to search for Bundles is a perfectly reasonable request to document that the
ProductSearchelement is for searching for MSI packages, not Burn bundles. -
Feature 4948 | Conditional assignment to variables requests the equivalent of the
SetPropertyelement for variables in a Burn bundle. This is something that needs a WIP, to figure out when and how variable assignments can be triggered and how it would all be authored. As it would be a non-trivial change, we opened it in WiX v4.x.
WiX v3.10.1
In celebration of WiX v3.10.1 shipping on schedule, we enjoyed refreshments, speeches, and debauchery, all of which were virtual. Then we went back to work.