Our dependency property setters are not being called, so I don’t think the problem is in the implementation of those setters. I suspect that the problem is with the order in which bindings are being established and evaluated when dynamically creating content due to a binding change. But I’m just guessing at this time.
I know a lot of our customers use a no-code-behind approach to M-V-VM. Actually, we designed GoXam before M-V-VM became popular, but we have not had to make any changes to accommodate that pattern.