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.
This one is not binded.
That one is a bit tricky since it needs the fields which are internal (in the bindings) and their logical names (for static fields) are already being used for (mostly string) instance properties (that returns values not the fields names).
Miguel, this is the case I talked to you about. Fields are internal ( a good thing in general) and properties using their name were exposed (but not to expose the fields).
Now a (not really) new API needs the fields... and most options looks ugly/confusing (and much different from objc source would look like when porting code).
I added the GetXXXDisplayName methods for the three cases that actually return values based on Apple's documentation