Bug 13739 - NSDate : timeIntervalSinceDate Not binded
Summary: NSDate : timeIntervalSinceDate Not binded
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll (show other bugs)
Version: 6.9.5.x
Hardware: PC Mac OS
: --- enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
Depends on:
Reported: 2013-08-04 08:58 UTC by Vincent Bellet
Modified: 2017-03-27 15:16 UTC (History)
6 users (show)

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


Description Vincent Bellet 2013-08-04 08:58:32 UTC
there is missing binding in NSDate.

All those NON static functions are not bind :

– timeIntervalSinceDate:
– timeIntervalSinceNow
– timeIntervalSinceReferenceDate
– timeIntervalSince1970

– isEqualToDate:
– earlierDate:
– laterDate:
– compare:

I know that you can convert it to a C# date but having the native API is easier when you convert a library.
Comment 1 Rolf Bjarne Kvinge [MSFT] 2013-08-05 07:03:02 UTC
- 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.
Comment 2 leslie.godwin 2014-09-30 02:31:21 UTC
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.

My 5c.
Comment 3 umakant_sharma 2017-03-24 12:54:18 UTC
Any updated on timeIntervalSinceReferenceDate.
Comment 4 Rolf Bjarne Kvinge [MSFT] 2017-03-24 16:43:17 UTC
@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.
Comment 5 umakant_sharma 2017-03-25 02:09:50 UTC
Any planing for below given
Comment 6 Rolf Bjarne Kvinge [MSFT] 2017-03-27 15:16:04 UTC
@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.

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