Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Unix time conversions in C# [duplicate]

I am trying to get the GMT in unix time. I use the following code:


        public static long GetGMTInMS()
        {
            var unixTime = DateTime.Now.ToUniversalTime() -
                new DateTime(1970, 1, 1, 0, 0, 0, DateTimeKind.Utc);

            return (long)unixTime.TotalMilliseconds;
        }

To then convert the unix time back to a DatTime object, I use this:


        public static DateTime UnixTimeStampToDateTime(double unixTimeStamp)
        {
            System.DateTime dtDateTime = new DateTime(1970, 1, 1, 0, 0, 0, 0);
            dtDateTime = dtDateTime.AddMilliseconds(unixTimeStamp).ToLocalTime();
            return dtDateTime;
        }

When I run it, the GetGMTInMS() 1320249196267. When I pass it to UnixTimeStampToDateTime() I get {11/2/2011 11:53:16 AM}

Which is fine. That is the correct time fro when I ran my code. The issue I have is when I try and put 1320249196267 into an unix time converter, such as this, it returns the totally wrong time.

The other issue, is i am in the eastern time zone. This returned the time in my time zone. Is this something that the DateTime object handles or am I not getting the GMT.

like image 709
user489041 Avatar asked Nov 02 '11 16:11

user489041


People also ask

Is Unix time same as UTC?

Unix timestamps are always based on UTC (otherwise known as GMT). It is illogical to think of a Unix timestamp as being in any particular time zone. Unix timestamps do not account for leap seconds.

How do I read a Unix timestamp?

To find the unix current timestamp use the %s option in the date command. The %s option calculates unix timestamp by finding the number of seconds between the current date and unix epoch.


2 Answers

"Unix timestamp" means seconds since the epoch in most situations rather than milliseconds... be careful! However, things like Java use "milliseconds since the epoch" which may be what you actually care about - despite the tool you showed. It really depends on what you need.

Additionally, you shouldn't be doing anything with local time. Stick to universal time throughout.

I would have:

private static readonly DateTime UnixEpoch =     new DateTime(1970, 1, 1, 0, 0, 0, DateTimeKind.Utc);  public static long GetCurrentUnixTimestampMillis() {     return (long) (DateTime.UtcNow - UnixEpoch).TotalMilliseconds; }  public static DateTime DateTimeFromUnixTimestampMillis(long millis) {     return UnixEpoch.AddMilliseconds(millis); }  public static long GetCurrentUnixTimestampSeconds() {     return (long) (DateTime.UtcNow - UnixEpoch).TotalSeconds; }  public static DateTime DateTimeFromUnixTimestampSeconds(long seconds) {     return UnixEpoch.AddSeconds(seconds); } 
like image 87
Jon Skeet Avatar answered Sep 19 '22 15:09

Jon Skeet


UNIX time is seconds since 1/1/1970, not milliseconds. Change the code to use seconds rather than milliseconds and it should work,

like image 33
arx Avatar answered Sep 19 '22 15:09

arx