WiX Online Meeting #120 Highlights
Tuesday, January 31, 2017
Today was the Ten Dozenth online meeting! (Rob seemed to like the roundness of 120, so I thought I'd respect that, even though I prefer powers of two. Or hex.)
Read more
WiX Online Meeting #119 Highlights
Tuesday, January 17, 2017
While attendance at today's meeting was light, we were not plagued by technical difficulties during recording and came to a decision about our presence on CodePlex. First, though, we triaged some bugs...
Read more
WiX Online Meeting #118 Highlights
Tuesday, January 3, 2017
Today was 2017's first WiX Online Meeting and, in a technical problem that does not bode well for the new year, no recording of the meeting is available. Just assume our tones were dulcet and our words were wise.
Read more
WiX Online Meeting #117 Highlights
Tuesday, December 20, 2016
Today was 2016's final WiX Online Meeting and, as appropriate for a time of year when many people use up their vacation days, we had a small crowd and quickly finished up triage so we could indulge in panicked last-minute shopping and nog-based beverages.
Read more
WiX Online Meeting #116 Highlights
Tuesday, December 6, 2016
OutOfMemoryException when saving newly generated WIX project, from @mediawolf, lets you watch the Visual Studio Devenv.exe slowly consume gigabytes of memory while hung. [[insert joke here about normal operating behavior]] This bug reproduces only when you uncheck the option to automatically save new projects when created. We took this bug in WiX v3.x to track down a root cause.
Read more
WiX Online Meeting #115 Highlights
Tuesday, November 22, 2016
Value containing !(wix) variable is used before being resolved, from @mediawolf, points out that when you use a bind-time variable like !(wix.WixVariable) as an attribute value, sometimes that value is used literally in other places. Sometimes the compiler uses one value to provide default values for other attributes, because it's helpful that way. But it expects the real value and a variable reference that won't be resolved until bind time isn't too useful. We agreed a warning would be useful before using such a value as a default for another; we took the issue in WiX v3.x.