Bug 57929 - Add support for using automatically generated assembly qualified names to export NSObject subclasses
Summary: Add support for using automatically generated assembly qualified names to exp...
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: master
Hardware: PC Mac OS
: --- enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Rolf Bjarne Kvinge [MSFT]
Depends on:
Reported: 2017-07-04 12:48 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2018-04-03 07:40 UTC (History)
2 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 for Bug 57929 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Rolf Bjarne Kvinge [MSFT] 2017-07-04 12:48:54 UTC
Something like this:

    [Register (UseAssemblyQualifiedName = true)]
    public class Foo : NSObject {}

this would solve problems where the same source file is included in multiple assemblies (for an example see bug #57915, this was also a problem with Xamarin.Auth and Xamarin.Social).

We don't want to generate assembly-qualified names for every NSObject subclass, since it would increase the binary size (it would increase the binary size for everybody, but only solve a problem very few people run into).
Comment 1 Kian Sims 2018-04-03 07:40:51 UTC Comment hidden (spam)