DateTime ticks inconsistent between .NET MF 4.2 and full .NET 4.0?
#1
Posted 06 September 2011 - 12:52 AM
#2
Posted 06 September 2011 - 02:56 AM
#3
Posted 06 September 2011 - 06:25 AM
Also, the initial system time (in absense of any time sync, or built in clock) is 1/1/2009:00:00:00.000 (128752416000000000 ticks)./// NOTES: Why origin is at 1/1/1601.
/// Current civil calendar is named as Gregorian calendar after Pope Gregory XIII as he made adjustments
/// in 1582 (read more at wiki http://en.wikipedia....gorian_calendar). Rules governing
/// leap years were changed from then. Also in that year month October was 21 days instead of usual 31.
/// This poses a problem on calculating date/time difference, leap years etc before 1582 using simple math.
/// For example 1500 was a leap year using old method while it is not using new. But in reality, as part of the
/// history it was leap year. Default CLR origin 1/1/01 gives wrong date time from years before 1582. For example
/// dates like 10/6/1582 does exist in history (see wiki), while CLR managed date/time will not throw an exception
/// if you are to create that date. To stay safe side 1/1/1601 is taken as origin, as was done for Windows.
#4
Posted 06 September 2011 - 12:39 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users