Vista changes .Net 2.0 Locale Names, sample work around custom cultures/locales
14th Nov 2006, 20:46 GMT
In order to follow RFC 4646 more closely (formerly RFC 3066 bis) we changed managed locale names in Windows Vista. Some applications had a dependency on the old names, in which case the suggested work around is to create custom cultures from the new locales with the old names. An example MakeCultures.cs to do just that is attached. Copy it somewhere, make sure %windir%\Microsoft.Net\Framework\v2.0.50727 is in your path and then compile & run it. Voilá!, new "old" cultures. path=%path%;%windir%\Microsoft.Net\Framework\v2.0.50727 csc /r:sysglobl.dll MakeCultures.cs MakeCultures.exe In addition to being a workaround, the .cs file is an example of making a trivial culture. Note that the "old" names are really non-standard, so the preferred solution is to make your app work with the correct names so that there aren't problems with other apps. For example, if someone made this their user locale, then their http-accept-language would be wrong when IE7 asked a server for a web page. This might get you out of a bind though until a better solution can be created.
Vista changes .Net 2.0 Locale Names, sample work around custom cultures/locales related news:
- ダレン ヒューストン社長から日本の開発者の皆様へのレター — Hiroyasu Kitagawa's Blog
- 'Unsinkable' Vista? — eWEEK Linux
- The Windows Vista Demo Environment — Softpedia - Latest news
- Hardwarefabrikanten verwachten hausse door Vista — Tweakers.net Nieuws
- deCarta Names VP (deCarta) — CADwire.net - All CAD industry news
- The Rising Tide of Vista; Vista: 'Polished, Speedy' — OSNews
- Una empresa española pone la música en los locales más "in" de EE.UU. al gusto del cliente — LA VANGUARDIA.es - Al Minuto
- Easily sort values with the .NET Array class's Sort method — TechRepublic.com
- Microsoft's Vista is released early — the INQUIRER
- Windows Vista, Office 2007 Code Leaked To The Net — InformationWeek News