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...
Status: ASSIGNED
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools (show other bugs)
Version: master
Hardware: PC Mac OS
: --- enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Rolf Bjarne Kvinge [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2017-07-04 12:48 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2017-07-04 12:49 UTC (History)
1 user (show)

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


Attachments

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).

Note You need to log in before you can comment on or make changes to this bug.