Yeah, I tried a few other things too. It seems to be specific to binding to an object reference. As soon as the object reference changes you get the double hit. It's not a big deal to put code in to skip normal processing if it is null, but it seemed odd.

So I'm curious, for this and other minor bugs, what happens with them now that we're at the end of the new version life cycle?

Thanks for confirming this.

-m@