Jérôme Laban

Also know that the evaluation of the DataContext is done on Loading. If the DataContext is changed afterwards, which is the case here, it won't get picked up. Set the...

The bindings will not be evaluated twice, as the root VM property is initially null because of the cast. It'll be populated once it's set, and won't change unless set...

We will not be able to change this behavior for a while (it touches the objects lifecycle in a big way). If you don't want to have the DataContext propagated...

Setting the DataContext explicitly should prevent the inheritance. If it still happens, try finding what sets it through the stack trace in the return from the screenshot above.

Setting the DataContext to null explicitly during the constructor should be enough to prevent the propagation.

Yes, as a workaround. For now it's not something we can fix without major changes.

@jeanplevesque You can also try setting the `DataContext` to null on the `Frame` so that the inheritance chain is stopped.

It should be enough, but if the datacontext is still propagated, it means that it's available in an intermediate control? Try setting it in codebehind, to be sure.

Thanks. That's still caused by the page being loaded too early, and the only way to fix that is to set the DataContext on the Page before adding it to...

Thanks. Then there's no current known workaround for this at this point.