[12 July 2007] Updated with culture names on list of effected cultures
The .Net patch of July 10th, ms07-049 http://www.microsoft.com/technet/security/Bulletin/ms07-040.mspx, changes culture names to use the new names on Windows XP/2003/2000 as well as Vista. changes culture names to conform to the standards. KB 939949, http://support.microsoft.com/kb/939949, deals with this issue and suggests the workaround posted here: http://blogs.msdn.com/shawnste/archive/2006/10/13/vista-changes-net-2-0-locale-names-sample-work-around-custom-cultures-locales.aspx .
This has been the Vista behavior since it shipped, and now the .Net 2.0 behavior for culture names is consistent between all versions of windows. Unfortunately this change can break applications that expect the old names. If that happens, the workaround of creating custom cultures might work for your application.
Old .Net Name
Potential problems experienced by applications could be:
Also the name change isn't pleasant, it does resolve issues with client/server names having difficulty communicating because of non-standard name uses. We continue to recommend names since LCIDs aren't available for all cultures/locales.
Hope this helps,