Culture Calendar TwoDigitYearMax ignored by .Net Date Parse

Question

0.00/5 (No votes)

See more:

I would expect the following to write a 2030 date into targetDate. It doesn't. It gives a 1930 date.

VB

Dim ci As CultureInfo = CurrentThread.CurrentCulture.Clone
ci.Calendar.TwoDigitYearMax = 2099
DateTime.TryParse("12/8/30", ci, DateTimeStyles.AssumeLocal, targetDate)

However if I set current culture to the clone then I get the expected (and required) 2030 date. But only if the code is running in a console app (Framework 2 or Framework 4.5 on Win7 Professional).

VB

Dim ci As CultureInfo = CurrentThread.CurrentCulture.Clone
ci.Calendar.TwoDigitYearMax = 2099

CurrentThread.CurrentCulture = ci
DateTime.TryParse("12/8/30", ci, DateTimeStyles.AssumeLocal, targetDate)

If the second fragment is run server side in a web app (Framework 2, Win7 Professional) then targetDate is _always_ a 20th century (19xx) date. This not desired behaviour and seems to
contradict the documentation.

Both the console apps. and the Web app. are run on the same (development) machine. Culture settings are not altered between runs.

Anyone else seen this?
Have you an explanation for what's going on?

Posted 24-Jun-13 3:51am

cigwork

Updated 24-Jun-13 4:21am

Nelek

v3

Add a Solution

Comments

lewax00 24-Jun-13 10:07am

Hmm...I guess the first thing to check here is: does CurrentThread.CurrentCulture return the same value in both cases? Could be coincidence that it worked in the first place.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ron Beyer · Accepted Answer · 2013-06-24T04:45:00

You probably also want to set the TwoDigitYearMax on the CurrentUICulture property of the CurrentThread. For some reason there are two culture objects, one for background threads, and one for UI threads. You only seem to be setting it on the background thread one and not the UI one.

It works in the console because there is no UI, so it uses CurrentThread.CurrentCulture.

EDIT---

If you want to add comments, please use the "Have a question or comment?" link below the solution :)

[cigwork note]

Quote:
Thanks. That works, had tried setting UICulture on its own, but tinkering seems to show that you need to set both culture properties _and_ hand in a cultureinfo instance to the TryParse call.