[英]DateTime.TryParse different results
As part of my unittests for an application I check a few datetime strings for their ability to get parsed. 作为我的单元测试应用程序的一部分,我检查一些日期时间字符串以获得解析的能力。 I recently noticed that on one machine the string
"0-02-20 11:36"
can get parsed to {2000-02-20 11:36:00}
by DateTime.TryParse(dateString, out parsedTimeStamp)
while on other machines it can't. 我最近注意到在一台机器上,字符串
"0-02-20 11:36"
可以通过DateTime.TryParse(dateString, out parsedTimeStamp)
解析为{2000-02-20 11:36:00}
,而在其他机器上不能。
string dt = "0-02-20 11:36";
DateTime parsedTimeStamp;
DateTime.TryParse(dateString, out parsedTimeStamp);
Console.WriteLine(parsedTimeStamp);
Parsing a DateTime
, like all parsing in the framework, is culture dependent . 解析
DateTime
,就像框架中的所有解析一样, 取决于文化 。
I would assume that on the exceptional machine, the culture settings use a yyyy-MM-dd
format, while on the other machines, the date format was MM-dd-yyyy
. 我认为在特殊的机器上,文化设置使用
yyyy-MM-dd
格式,而在其他机器上,日期格式是MM-dd-yyyy
。
To work around this, you can parse in a specific culture or using an invariant culture. 要解决此问题,您可以解析特定的文化或使用不变的文化。
DateTime.TryParse(dateString, CultureInfo.InvariantCulture, DateTimeStyles.None, out parsedTimeStamp);
It turns out there are quite a few of these cultures: 事实证明,这些文化中有不少文化:
foreach (var c in CultureInfo.GetCultures(CultureTypes.AllCultures))
{
if (c.DateTimeFormat.ShortDatePattern == "yyyy-MM-dd")
{
Console.WriteLine("{0}: {1}", c.DisplayName, c.DateTimeFormat.ShortDatePattern);
}
}
Korean: yyyy-MM-dd
Polish: yyyy-MM-dd
Albanian: yyyy-MM-dd
Swedish: yyyy-MM-dd
Khmer: yyyy-MM-dd
Sinhala: yyyy-MM-dd
Korean (Korea): yyyy-MM-dd
Polish (Poland): yyyy-MM-dd
Albanian (Albania): yyyy-MM-dd
Swedish (Sweden): yyyy-MM-dd
Khmer (Cambodia): yyyy-MM-dd
Sinhala (Sri Lanka): yyyy-MM-dd
Sami, Northern (Sweden): yyyy-MM-dd
French (Canada): yyyy-MM-dd
Sami, Lule (Sweden): yyyy-MM-dd
Sami, Southern (Sweden): yyyy-MM-dd
Sami (Southern): yyyy-MM-dd
Sami (Lule): yyyy-MM-dd
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.