Issue labels
During the last meeting, I volunteered to look at how other open-source projects on GitHub use labels in their issues. You won't believe what happened next! Or maybe you will; it's straightforward web research, after all. Take a look at my blog post to see the results and details we discussed.
Issue triage
Custom FailureMessageText on ExePackage failure, from @jimmyca15, asks for the ability to show a custom message when a package fails in a bundle. As UI is the domain of bootstrapper applications, I suggested this should be a WixStdBA feature whose plumbing other BAs could borrow. We took this in WiX v4.x and applied the shiny new
wip-requiredlabel.WiX Toolset v.4.0.0.5205 requests .NET Framework 3.5.1, from @nordickeal, mentions that even WiX v4 requires .NET 3.5.1. WiX v4.0 will not require .NET 3.5.1 so we took this bug in WiX v4.0.
Let PreprocessorExtensions implement IDisposable, or add a method to indicate that all files have been processed, from @Ganon11, requests an additional "done" callback so a preprocessor extension can know when all files have been through the preprocessor. We took this in the WiX v4.x milestone.
Reboot after installing .NET Framework, Burn tries to load the original source from the wrong source., from @henning-krause, reports a problem when using a compressed bundle that requires a mid-chain reboot and that was renamed after it was built. We took this in WiX v4.x.
Install NuGet package freezes Visual Studio 2017 on OAWixProject.Save, from @ingobau, reports a problem in Votive's automation support. We took this issue in WiX v4.x.
VS 2010 Extension: Install Error : System.IO.PathTooLongException on Windows XP and Server 2003, from @robi-wan, says that the Votive extension for Visual Studio 2010 doesn't install on Windows XP(!) due to path-length limitations. Rob volunteered to squish various names to try to fit into MAXPATH characters.
cURL used in WiX build (both v3 and v4) has a "highly critical" security flaw, from @BMurri, says we shouldn't use a vulnerable version of Curl in the WiX build process. We don't but we used to and left behind the Curl binaries. Rob volunteered to hunt them down.
ERRORLEVEL returns 1 after successful installation, from @AlexL3, claims Burn is returning a nonzero exit code for a successful installation. We took the issue in WiX v4.x for someone to investigate.
VS2017DevEnvSearch does not find VS2017 if there are BuildTools installed., from @jbialobr, reports a problem in the new-to-WiX-v3.11 support for detecting Visual Studio 2017. Heath agreed there's a bug and opened a pull request we agreed to take for WiX v3.14.
Feature request: Support RemotePayload for Payload elements, from @nirbar, requests support for download-only payloads separate from a containing package. We agreed this is an interesting use case and assigned the issue to WiX v4.x.
Accessiblity Name for EULA in RtfLicense.xml theme is wrong, from @richardstanton, reports that WixStdBA themes aren't laid out correctly for accessibility tools. We took this in WiX v4.x.
Dotnet CLI Tools - The WiX Toolset v3 build tools must be installed to build, from @stoned72, reports a problem building a .wixproj with .NET Core SDK tools. Rob was interested in the topic so volunteered to take a look.
Add support for XSLT 2.0 in transforms, from @letmaik, requests support for XSLT 2.0 in Heat. We took the request in WiX v4.x for someone to investigate.