CurrentCulture incorrectly defaulting to en-US in ASP.net

I have just migrated around 100 ASP.net sites from IIS 6 on Windows Sever 2003 to IIS 7 on Windows 2008. I’ve just noticed that various pieces of code that use things like DateTime.Parse have started kicking up errors “String was not recognized as a valid DateTime”. I’ve tracked this down to the fact that the CurrentCulture of the sites is defaulting to ‘en-US’ and so my UK users are inputting dates in an unexpected format.

Javascript Date Localization

I’m working with an ASP.NET app with localization and globalization. I’m having some difficulty understanding how to get the Date() function in javascript to work properly given the user’s environment. My user base is split between Mexico (spanish) and the US (english). Since the Mexico date format is dd/mm/yyyy and the english format is mm/dd/yyyy, the standard Date(strDate) javascript constructor does not work for me.

comma decimal seperator in asp.net mvc 5

im desperately trying to make asp.net work with the comma symbol as the decimal seperator but this seems to be a lot harder then necessary… i’ve done everything that’s in this tutorial http://www.asp.net/mvc/overview/getting-started/introduction/examining-the-edit-methods-and-edit-view tried this in the root web config <system.web> <globalization culture="de-DE" uiCulture="de-DE" /> </system.web> stepped through the jQuery code – the globalization there … Read more