0

In my web.config file I have this line:

<globalization culture="auto:en-GB" uiCulture="auto:en-GB" requestEncoding="utf-8" responseEncoding="utf-8" responseHeaderEncoding="utf-8"/>

ASP.Net nicely takes care of all date/time formats. Applying the following code in a sample page...

Protected Sub Page_Load(sender As Object, e As EventArgs) Handles Me.Load
    txt.Text = New DateTime(2010, 1, 25).ToString()
End Sub

Protected Sub btn_Click(sender As Object, e As EventArgs) Handles btn.Click
    Dim dt As DateTime = Convert.ToDateTime(txt.Text.Trim())
    Trace.Warn(dt.ToString())
End Sub

With a browser, set to English (UK) I see the date displayed as

25/01/2010 00:00:00

On pressing the button and converting this back to a DateTime value, it works perfectly.

If I change my browser (Chrome) settings to Norwegian Bokmal, and load the page, I see this:

25.01.2010 00.00.00

This again is correct, but, if I then submit the form, ASP.Net crashes:

String was not recognized as a valid DateTime.

Line 9: Dim dt As DateTime = Convert.ToDateTime(txt.Text.Trim())

Why is this happening? Surely if ASP.Net has the sense to display dates based on culture settings, it should be able to read them? I've tried English UK and English US and both work as expected, plus others, so it seems linked to Norwegian in some manner.

EvilDr
  • 8,943
  • 14
  • 73
  • 133

2 Answers2

2

Finally found the answer. It is a bug in the .Net framework for v4.0+.

It has been reported in Microsoft Connect, and a temporary workaround is detailed here. Apparently this is problem strictly related to Windows 10:

Windows 10 changes the date and time formatting settings for some cultures. Of particular concern are seven cultures for three different regions:

  1. Finnish
  2. Norwegian Bokmål (“Norway” and “Svalbard and Jan Mayen” variants)
  3. Serbian (variants “Cyrillic, Kosovo”, “Latin, Montenegro”, “Latin, Serbia” and “Latin, Kosovo”).

For these seven cultures, Windows 10 changes the date and time separators to be the same. For example, in Finnish, the standard date format used to be 26.8.2015 21:08, while it is now 26.8.2015 21.08 – note the subtle change in the time separator.

In all currently released versions of .NET, the DateTime.Parse method has a shortcoming: It always fails to parse a date or a date+time combination in a culture where the date/time separators are the same character. This bug, together with Windows 10’s culture changes, breaks the previously hard rule of DateTime.Parse always being able to parse the culture’s default DateTime representation. Now, DateTime.Parse(DateTime.Now.ToString()) no longer works under the described conditions. Neither does DateTime.Parse(DateTime.Now.ToShortDateString()), which is somewhat counterintuitive since the changed time separator isn’t even involved, but true nonetheless – the parser thinks it’s parsing a time instead of a date.

An official patch will be released in September 2015.

EvilDr
  • 8,943
  • 14
  • 73
  • 133
0

Use the Convert.ToDateTime(string, IFormatProvider) overload to specify the CultureInfo to use.

Binkan Salaryman
  • 3,008
  • 1
  • 17
  • 29
  • I thought that was done automatically if IFormatProvider was not used as part of the web.config/default globalization settings? – EvilDr Sep 08 '15 at 16:00
  • The MSDN states for the (string) overload: ``the return value is the result of invoking the DateTime.Parse method on value using the formatting information in a DateTimeFormatInfo object that is initialized for the current culture``; I doubt this refers to the default application culture info you assigned, but the culture info of the machine running the application. – Binkan Salaryman Sep 08 '15 at 16:10
  • Yes but it then says, `If provider is Nothing, the DateTimeFormatInfo for the current culture is used` which allows for easy globalization, or, it *should*. Even setting current culture on every PreRequest fails to stop the error. I think this may be a .Net bug for the Norwegian language as en_GB and en_US both work fine (among others)... – EvilDr Sep 09 '15 at 09:21
  • When I run a test of `Convert.ToDateTime` specifying the Norwegian culture as IFormatProvider, it still fails. – EvilDr Sep 09 '15 at 09:30
  • How did you specify he norwegian culture? You may take a look at [this thread](http://stackoverflow.com/questions/13159969/trouble-with-cultureinfo-for-norway), where a discussion about neutral languages arose. – Binkan Salaryman Sep 09 '15 at 10:04
  • `no` and `nb` are both correct ways, but it fails with both (and also fails with `nb-NO`. Very very strange – EvilDr Sep 09 '15 at 11:28