Just wondering if ".false" is a typo?

yes it should have been'false'
good catch !

CanDidRangeBeaconsSatisfyingConstraint be shortened toDidRangeBeacons - since the params are different it won't cause a namespace issue, right?

Good catch! It was my first attempt too - but sadly it can't :(

The problem are that:

• the name is already used in the type (even if overloads are fine most of the time);
• a*Delegate type;
• it uses[EventArgs];

so this cause a conflict in the generated code.

I don't have this PR built right now - but I'll update the comment with the code (easier to see what's happening this way).

Update

So the[EventArgs] attribute is used in conjunction with theEvents property of[BaseType]. This allows us to expose C# events as a better alternative (there are gotchas) to implementing a*Delegate.

[BaseType(typeof(NSObject),Delegates=newstring[]{"WeakDelegate"},Events=newType[]{typeof(CLLocationManagerDelegate)})]partialinterfaceCLLocationManager{

But the extra events means a conflict because we already have aDidRangeBeacons method inCLLocationManagerDelegate, so the generator already created an event using that name:

publiceventEventHandler<CLRegionBeaconsRangedEventArgs> DidRangeBeacons{add{ EnsureCLLocationManagerDelegate().didRangeBeacons+= value;}remove{EnsureCLLocationManagerDelegate().didRangeBeacons-=value;}}

and we can't overload events in C# (even if the args are different).

So to avoid the compiler error a new, different name must be used - and I chooseDidRangeBeaconsSatisfyingConstraint

When do we useBindAs?

There's a few cases, the most common one isNSNumber, like above. Another one are to support "smart enums" (using a C# enum that maps to severalNSString constants).

So for some API Apple prefers to use a reference type, likeNSNumber, over a more specific value type. Why ? mainly because they want a nullable properties

But

NSNumberMajor{get;}

does not tell the API consumer if it should except ashort (like it's meant to), afloat or even abool. That does not create a very discoverable API and we can do a lot better in C# with nullable? types :)

Why not

short?Major{get;}

Because our runtime must know this anNSNumber natively - e.g. it's needed to allow us to override the property in a subclass and have some ObjC code call us. So the declaration remains anNSNumber but we give the generator a hint to add extra (conversion) code to expose a nicer API to our developers.

Also we have some docs about it :)https://docs.microsoft.com/en-us/xamarin/cross-platform/macios/binding/objective-c-libraries?tabs=macos#binding-nsvalue-nsnumber-and-nsstring-to-a-better-type

Thank you both for the detailed explanation! 👍