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.
the set should probably map to ExpandableListView.setAdapter
That's an interesting expectation. But generally, this property being readonly is how Mono.Android.dll is designed to be.
We don't manually go through the vast android.jar API. Instead, we *automatically* generate API based on obvious rules. If there were setExpandableListView() method in Java ExpandableListView class, then it should be mapped to a setter. But setListView() does not follow that rule, so it isn't converted *by design*.
If we still treat this as special case and insert some special logic in our managed API generator, things will get complicated, which makes the entire Mono for Android ecosystem hard to maintain, buggy and distracted while we have lots of things to improve. I don't think it is good for everyone.
If there are similar patterns that can be turned into automatic API conversion, then we should revisit and consider about making certain logic.