Renouncement
While this question looked like a potential duplicate , it was resolved by referring to IsAmbiguousTime
. This does not solve my problem, since the time when I notice a discrepancy does not report ambiguity.
Question, then ...
While timeanddate.com says that Morocco is observing daylight saving time from April 3 to July 31 this year and the current time provided by worldtimeserver.com seems to imply that it is, .NET TimeZoneInfo
does not report Casablanca time as having any AdjusmentRules
or AmbiguousTimeOffsets
corresponding to 2011.
Indeed, if you set my computerβs clock to a time in Casablanca, it will set the current time one hour earlier than what is indicated as the current time in Casablanca through online resources.
Is the .NET library inaccurate in this regard, or are all other sources to blame? Given that the .NET library is an inaccurate source here, is this a common problem? The fact that I learned about this instance simply because a mismatch occurred in the first time zone in the .NET enumeration is a concern. Is this the basis for a local database that I can update myself?
source share