WiX Online Meeting #178 Highlights

Issue triage

• ExitDialog unexpected behavior, from @wqweto, reports a bug originally found in a prerelease version of WiX v2(!). A minor tweak to the WixUI exit dialog seems in order, so we took the issue into WiX v4.0 and I volunteered to take a look.

• Allow more controls on the installation successful page, from @jozefizso, requests — and provides a pull request for — additional controls to be displayed upon a successful bundle install. We’re generally strict about continuing to take changes into WiX v3.14 but as this is simple and useful, we agreed.

• Package not cached after bundle upgrade, from @NMGo, demonstrates what appears to be a deficiency in how Burn manages the package cache when packages are just cached instead of cached and installed. Rob suggested it would be worth investigating whether Burn should register a dependency when a package is cached, to in effect reference-count the cache. We took the issue into WiX v4.0 if someone were interested in performing that investigation.

• Heat project harvesting fails if using unusual system region, from @jmairboeck, reports a problem using Heat.exe when using an exotic region setting in Windows. That’s worth looking into so we took the issue into WiX v4.x.

• Documentation advises wrong calling convention for native custom bootstrapper applications, from @AceFuture, turns out to indeed be a documentation bug, though a bit different than the reporter thought at first. We took the issue into WiX v4.x and I volunteered to make a fix.

• Custom action dll is not in valid format, from @andrey-ivanov, reports an odd error when signing a managed custom action. We took this into WiX v3.14 as we’d consider a fix there if it’s a generally-occurring issue.

• VsixPackage ActionText, from @rickpapo, requests a feature to allow the user to specify an action message when installing a .vsix package using WixVSExtension’s VsixPackage element. That’s certainly a reasonable feature request, so we took the issue into WiX v4.x.