Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 13739 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
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
there is missing binding in NSDate.
All those NON static functions are not bind :
I know that you can convert it to a C# date but having the native API is easier when you convert a library.
- timeIntervalSinceReferenceDate is bound as the SecondsSinceReferenceDate property.
For the rest we've tried not to bind ObjC API which have an exact .NET equivalent, so we'll have think a bit about those.
I agree about the not binding exact .NET equivalents.
However it needs to be documented with attributes or something so one can be aware of the equivalent to use.
IDE can look for those attributes and show the alternative.
Any updated on timeIntervalSinceReferenceDate.
@Umakant, see comment #2: timeIntervalSinceReferenceDate is bound as the SecondsSinceReferenceDate property.
> – timeIntervalSinceDate:
> – timeIntervalSinceNow
> – timeIntervalSince1970
There are still not bound.
> – isEqualToDate:
> – earlierDate:
> – laterDate:
> – compare:
These are all bound now.
Any planing for below given
@Umakant, we don't currently have a plan for these methods, but it should be easy to get something similar using already existing .NET api.