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.
Xamarin Forms does a pretty poor job of indicating to the developer where they've made a mistake in the binding expressions. One example of this is the exception message "Can't resolve name on Element". This exception message would be far more useful if it told use the actual name it was unable to resolve. It could go further by indicating the element on which it was trying to resolve the name, or the binding expression that caused the error, but just giving the name that it couldn't resolve would make this exception message 1000x times more useful.
As this is not specifically a bug, I would suggest possibly starting a discussion on the X.F Evolution forum regarding potential enhancements to error messages such as this one. We also greatly welcome PRs from our community.