Bug 5775 - Derived classes don't see private exported methods from base classes
Summary: Derived classes don't see private exported methods from base classes
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 5.3.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on: 1353
Blocks:
  Show dependency tree
 
Reported: 2012-06-20 09:06 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2013-06-03 03:35 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Test case (8.08 KB, application/zip)
2012-06-20 09:06 UTC, Rolf Bjarne Kvinge [MSFT]
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FIXED

Description Rolf Bjarne Kvinge [MSFT] 2012-06-20 09:06:47 UTC
Created attachment 2093 [details]
Test case

See attached test case.

* Run test case.
* Tap somewhere.

Selector not found exception will be thrown.

* Change MyView.HandleTap from private to internal and try again.

Note how no exceptions are thrown now.
Comment 2 Rolf Bjarne Kvinge [MSFT] 2012-06-21 06:01:30 UTC
This comes from http://lists.ximian.com/pipermail/monotouch/2012-June/010089.html

The nasty issue is that you can have a class that's working perfectly fine, but then you create a subclass (without any code at all inside it), and suddenly that subclass doesn't work.
Comment 4 Mikayla Hutchinson [MSFT] 2012-06-21 12:48:16 UTC
FWIW, this seems the same as bug 1449.

If someone has exported a member, they have explicitly made it public to Obj-C, even if it's private to C#. Having such things break as soon as they're subclassed isn't useful or consistent at all, IMO.
Comment 5 Rolf Bjarne Kvinge [MSFT] 2013-06-03 03:35:11 UTC
This has been fixed in the new registrar.