dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: .NET
Expertise: Beginner
Nov 18, 2008

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Problem with Parsing Date in Different Regions

Regional settings, especially dates, are always a problem in code. For example, suppose the product is developed in U.S. and deployed in UK. Users entering dates in UK format would cause DateTime.Parse exceptions (because the input would not be recognized as a valid DateTime). The shortest fix for this problem is to use the DateTimeFormatInfo object during parsing, as shown below:

System.Globalization.DateTimeFormatInfo MyDateTimeFormatInfo = new System.Globalization.DateTimeFormatInfo();
MyDateTimeFormateInfo.ShortDatePattern = "M/d/yyyy";
string StartDate = DateTime.Parse(dt.ToString("MM/dd/yyyy",MyDateTimeFormatInfo); 
The preceding code should work for all short-date entries, regardless of the local machine settings.

Srinath MS
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
×
We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date