Bug 27722 - ContentView.Content Property Is Not Bindable
Summary: ContentView.Content Property Is Not Bindable
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.3.5
Hardware: PC Windows
: Normal minor
Target Milestone: ---
Assignee: Jason Smith [MSFT]
Depends on:
Reported: 2015-03-05 19:44 UTC by Michael
Modified: 2015-05-19 14:29 UTC (History)
4 users (show)

Tags: contentview bindings
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Michael 2015-03-05 19:44:22 UTC

It appears that the ContentView.Content Property is not a bindable property.  I am sure this is rather obvious/common knowledge at this point, or maybe a known issue, but every property should be bindable by default if at all possible.  If there is a known issue around this, then it would be great to know.  Just point me in the direction.  Also, in the case of a ContentView, it would be great to have the Content property be of type Object, and have Xamarin.Forms determine the default DataTemplate used for the provided object, ala WPF.  That is one of its coolest features. :)

Please let me know if there is something completely obvious around this issue that I am overlooking.

Thank you,
Comment 1 Jason Smith [MSFT] 2015-05-19 14:29:15 UTC
This is not currently planned, thank you for your feature request.