Have Geek Brain

Can anyone explain how the DaylightSavingsRule can have "StartMonth" after "EndMonth"?

Using C # (.NET framework) I go through all the TimeZones and their AdjustmentRules ... and for "Mauritius Standard Time" {(GMT + 04: 00) Port Louis)} - the adjustment rule is as follows:

IsFixed = false;
DaylightTransitionStart.Month = 10;
DaylightTransitionEnd.Month = 1;

From what I understand, "IsFixed = false" means that I am not using the "StartDate" and "EndDate" fields ... but I need to use DaylightTransitionStart and End to dynamically determine if the time is in daytime or not.

The PROBLEM here is that for about 30 transition rules, "StartMonth" is AFTER "EndMonth"

How does DaylightSavingsTime start in October 2008 and end in January 2008?

Please help me figure this out ... once I get over this hurdle I should have a complete "convert any time to and from UTC with any time zone for the whole story". The SQL function is written.

+1


source to share


5 answers


The time period may not logically end before it starts, but you might be guessing that these months refer to months in the same year when the OCT may actually be in 2008, but JAN is in 2009.

Think of it as a circular list.



The DaylightTime class uses DateTime for both the start and end of daylight savings time, so the year is specified.

+5


source


Wouldn't that be for countries south of the Equator?



+4


source


This thing is called the southern hemisphere. You may have heard about this.

In Australia, summer savings starts around October and ends around March (in states where available).

+3


source


may be in the southern hemisphere, DST starts in October and ends with a march in parts of Australia.

+2


source


Two different years. e.g. start of year 09 end of year 10

+1


source






More articles:


All Articles