Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
I lost hours workring out how these work, even raising bugs here, and if it wasn't for Adam Kemp on the forums I'd be totally suck.
Since then I've seen 2 forum posts with identical questions. That's in just 24 hours.
I think it shows that your documentation is really bad at explaining the nuances of setting up bindings for custom controls.
There are some specifics which you need to let people know:
1. the binding properties must be static,
2. they must match the name of the property,
3. the getter/setter of the property won't ever be called, and breakpoints there won't work,
4. you need to use the observe callbacks to find out when changes occur.
5. The types must match exactly,
6. The bindings will fail silently if none of the above is observed.
None of this is obvious, and it's really easy to screw up.
@George, We apologise for the issues you faced for binding documentation and great thanks to bring this issue via reporting a bug. I am confirming this issue so that Developer can figure out it and approach to right person to update the document.
Thanks for your efforts!!
Thanks again George. We always strive to make sure our documentation covers as much as possible, but feedback is always helpful. We've moved this feedback over to the documentation team's internal tracker, and I'm going to mark this as RESOLVED ANSWERED for now.
Please feel free to REOPEN with additional questions.