It turns out that for customers that are deriving from TemplatedView run into issues with the ContentPresenter and the binding for the Content property.
For customers that don't trim their apps, the fallback to reflection would match the behavior they were experiencing in .NET 8
For customers that trim/Native AOT their apps, the fallback likely won't do anything but it also won't produce any warning.
AFAIK we currently don't have any docs that would mention how to implement custom TemplatedView that could be updated to mention that the "proper" way to do this is to implement the object IContentView.Content property in the derived class. I added runtime warning but I'm not sure how many developers will actually see this or just miss it completely.
cc @PureWeen @mattleibow @StephaneDelcroix @davidbritch
Description of Change
It turns out that for customers that are deriving from
TemplatedViewrun into issues with theContentPresenterand the binding for theContentproperty.AFAIK we currently don't have any docs that would mention how to implement custom
TemplatedViewthat could be updated to mention that the "proper" way to do this is to implement theobject IContentView.Contentproperty in the derived class. I added runtime warning but I'm not sure how many developers will actually see this or just miss it completely.cc @PureWeen @mattleibow @StephaneDelcroix @davidbritch
Issues Fixed
Fixes #25947