是NET的DateTime的方法能够识别闰秒的？ [英] Are .Net's DateTime methods capable of recognising a Leap Second?

问题描述

随着闰秒在地平线上今年六月这让我怀疑是否.NET Framework是闰秒知道？额外二是6月30日的最后一秒后要插入所以UTC将正式成为：

With a Leap Second on the horizon for June this year it got me wondering whether the .Net framework is leap second aware? The extra second is to be inserted after the last second of June 30th so UTC will officially be:

2012 June 30,     23h 59m 59s
2012 June 30,     23h 59m 60s
2012 July  1,      0h  0m  0s

是.NET Framework能够处理呢？它甚至不管 Windows未闰秒意识到？这是否会影响在单应用程序的O / S的那个的运行是的闰秒认识？

Is the .Net framework capable of handling this? Does it even matter if Windows is not Leap Second aware? Will this affect apps in mono running on O/S's that are Leap Second aware?

编辑：

要在此展开一点点我正在设想这样一个场景：在Linux上一个基于Java的解决方案（也就是闰秒感知）调用.​​NET Web服务传递的东西是在Java中一个有效的时间戳，但出来的界.NET。是否有迎合它的任何框架（像野田时间也许）？

To expand on this a little bit i'm envisioning a scenario where a Java based solution on Linux (which is Leap Second aware) calls a .Net Web Service passing in something that is a valid timestamp in Java but is out of bounds for .Net. Are there any frameworks that cater for it (Like Noda Time perhaps)?

推荐答案

没有 -

有一个单一的滴答再presents百纳秒或千万分之一秒。有在一毫秒万蜱

A single tick represents one hundred nanoseconds or one ten-millionth of a second. There are 10,000 ticks in a millisecond.

这个属性重新$ P $的价值psents自午夜12:00:00，1月1日，0001，从而重新presents DateTime.MinValue以来经过的100纳秒间隔数。 它不包括蜱是由于闰秒的数目。

The value of this property represents the number of 100-nanosecond intervals that have elapsed since 12:00:00 midnight, January 1, 0001, which represents DateTime.MinValue. It does not include the number of ticks that are attributable to leap seconds.

来源：<一href="http://msdn.microsoft.com/en-us/library/system.datetime.ticks.aspx">http://msdn.microsoft.com/en-us/library/system.datetime.ticks.aspx

这篇关于是NET的DateTime的方法能够识别闰秒的？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！