Tom Donovan wrote: > > I'd vote to fix it in 2.2.4 rather than deal with the noise - but > personally I'm happy either way since I now know the workaround.
We won't - 2.2.4 is done. We could scuttle 2.2.4, but given the overwhelming improvements I'm really loathe to do that. Let 2.2.4 live, and pick up 2.2.5 soon. We can't help it when MS doesn't follow their own documented API /shrug
