Bug 12501 - Implement opt-out of automatic registration of NSObject derived classes
Summary: Implement opt-out of automatic registration of NSObject derived classes
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 6.3.x
Hardware: PC Windows
: --- enhancement
Target Milestone: 7.2.0 (iOS 7.1)
Assignee: Bugzilla
Depends on:
Reported: 2013-05-31 17:34 UTC by Oliver Weichhold
Modified: 2014-05-13 07:30 UTC (History)
4 users (show)

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

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:

Description Oliver Weichhold 2013-05-31 17:34:01 UTC
Since classes derived from derived from NSObject using Generic Arguments now cause a runtime exception, it would be helpful if there was a way of opting out of automatic registration of those classes. Not being able to use generic with for example UIViewController derived classes makes implementing some common scenarios more complicated than necessary.
Comment 2 PJ 2013-11-19 16:44:39 UTC
This bug was targeted for a past milestone, moving to the next non-hotfix active milestone.
Comment 3 Rolf Bjarne Kvinge [MSFT] 2014-05-13 07:30:48 UTC
Support for generic subclasses of NSObject has been implemented in Xamarin.iOS 7.2.1 (with the new registrar), so this should be a non-issue now.