Today we triaged incoming issues and in an endurance marathon of triage, also triaged WiX v4.0 issues to determine which need to be resolved before we can ship WiX v4.0 Preview Zero.
CustomActionattributes should use
Refsuffixes instead of
Key, from @barnson, brings up a bit of philosophy: The use of
Keyin attribute names is mostly a throwback to Windows Installer's use of databases, with their tables, rows, columns, and keys. We decided that using
Refwas the most consistent with other WiX concepts like the many elements ending in
ComponentGroupRefbeing my personal favorite).
Specifying inner text where it was previously allowed should be an error, from @rseanhall, requests now that inner text content has been moved to attributes, that accidentally using inner text should be an error rather than silently ignored.
WiX v4 assemblies should be strong-name signed, from @barnson, is fairly self-explanatory. WiX v3 assemblies were always strong-name signed, which is a .NET Framework requirement if tools that consume those assemblies is itself strong-name signed. WiX v4 assemblies so far haven't been strong-name signed.
light.exe creates "corrupt" .cab files, from @MarkoKaiser, is a disconcerting bug but we asked for a repro case to ensure we're getting the scenario right and haven't heard back. We'll keep this one around until next meeting.
We also received a big set of accessibility bugs against WixStdBA that we're tracking in WixStdBA accessibility bugs:
[Keyboard Navigation - WIX - Setup Option] When user select OK button which available on the "Browse For Folder" popup window, then keyboard focus is not visible on the "Install location" editable field, from @tgugler
WiX v4 Preview Zero triage
We triaged the following issues as needing to be fixed before we can declare Preview Zero of WiX v4.0 ready. Including the bugs we triaged before, we have 28 bugs to hit Preview Zero: another unfortunate but not unexpected upward trend.