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.
In reference to case #29889
Outlets generated in designer.cs files have private access. Any classes that inherit from this view will not be able to access any of the outlets, and will throw an exception in Objective-C. Please generate outlets with protected access so that subclasses can make use of them.
The fact that they're properties is an implementation detail of the outlet mechanism. Think of them as private fields. You can easily expose them via public/protected properties.
The fact they cannot be accessed from obj-c is a bug in the bridge (obj-c does not have a concept of accessibility, everything exposed to obj-c should be accessible from obj-c). It's bug 1449.
*** This bug has been marked as a duplicate of bug 1449 ***