WiX v5 is here! Let us help.
WiX Online Meeting 242 Highlights
Thursday, August 25, 2022
Two new issues and a handful of old issues to triage -- surely this would be a quick meeting? You might think so, unless, you know, you've watched any of the other 241 meetings we've held and seen how rarely that happens.
Read more
WiX Online Meeting 241 Highlights
Thursday, August 11, 2022
Today's meeting had more issues to triage than typical yet they were all opened by Rob, Sean, or me. Did we do this to punish ourselves? Maybe but mostly because we're encountering issues as we use WiX itself. That's good news for WiX v4's readiness for a wider audience. Soon!
Read more
WiX Online Meeting 240 Highlights
Thursday, July 21, 2022
Today's meeting was triage. Just triage. We had our normal incoming triage and we also started, as promised, to review the current slate of issues scheduled to be addressed in WiX v4. Refining that list will help us figure out when WiX v4 is ready for mass consumption and on the road to be released!
Read more
WiX Online Meeting 239 Highlights
Thursday, July 7, 2022
As promised, today we did our normal triage and we risked taunting the Demo Gods by having Rob run through the Windows Sandbox work I've done to run the WiX integration tests in a quick and easy virtual machine provided by Windows. Did the Demo Gods retaliate?
Read more
WiX Online Meeting 238 Highlights
Thursday, June 23, 2022
Today's meeting had only a handful of issues, none of which caused our (in)famous long design discussions, so we had our first meeting of less than 30 minutes in a long time. I'd hoped to share my findings about running the WiX runtime tests in Windows Sandbox but, alas, life interfered with that goal. Next meeting for sure!
Read more
WiX Online Meeting 237 Highlights
Thursday, June 9, 2022
Today's triage focused primarily on the rise of reports of problems installing Votive into the latest point release of Visual Studio 2022. My suggestion of going back to Notepad-based development was not broadly accepted. We're keeping an eye on the problem and hope to hear back from Visual Studio folks by the next meeting, so stay tuned.
Read more