Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I deployed a MVC3 Application that works well in development environment, that's because the date format in the develop machine it's dd/mm/yyyy. But When The application was deploy in the server starts to getting errors in the server side for not valid Dates, because in the server the format of date it's mm/dd/yyyy. Now my question it's Do i need to configure the server?? or only the IIS 7.0 for this specific culture??. Whatever the answer was please let me know how can I do this. I'm working in a windows server 2008 R2 and iis 7.5

share|improve this question
up vote 1 down vote accepted

If the only challenge for cultures is for date formats that will work on any server, do yourself a favor and don't use culture-specific date formats. Use a culture-neutral date format:

yyyy-MM-dd is the same everywhere.

If you really want to localize your app to a specific culture, there is a <globalization> element in web.config where you can specify the culture.

Internationalization is a vast topic. Entire books have been written about it. There may be multiple culture issues to solve. You're asking about the server culture, but what about the clients that connect? If you really want to accommodate cultures, you would get the client culture from Accept-Languages part of the HTTP Header.

globalization element in web.config

Globalization, Internationalization and Localization in ASP.NET MVC 3, JavaScript and jQuery

jQuery Globalization Plugin from Microsoft

.NET Internationalization: The Developer's Guide to Building Global Windows and Web Applications

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.