In .Net 4.0 the following code throws an InvalidOperationException with the message \"Specified element is already the logical child of another element. Disconn
There are times when it makes sense for a child to have more than one logical parent, for instance in layout-to-layout animation. I'm guessing the WPF team decided it was time to let developers decide when and how to use this instead of disallowing it.