Vista changes .Net 2.0 Locale Names, sample work around custom cultures/locales

Problems compiling resources in .Net 2.0 apps after updates.

I'm not a Klingon — Tue, 14 Nov 2006 23:18:08 GMT

In order to conform to RFC 4646 (replaces RFC 3066), we updated the names of some locales, which can

Updated custom culture sample workaround for the .Net 2.0 Culture Name Change

I'm not a Klingon — Tue, 05 Jun 2007 21:39:17 GMT

I updated the sample for Vista changes .Net 2.0 Locale Names, sample work around custom cultures/locales

Security patch breakes some culture names for .Net 2.0 on Windows XP/2003/2000

I'm not a Klingon — Thu, 12 Jul 2007 03:09:27 GMT

The .Net patch of July 10th changes culture names to conform to the standards. KB 939949 deals with this

Security patch MS07-040 for .Net 2.0 breaks some culture names for .Net 2.0 on Windows XP/2003/2000

Noticias externas — Thu, 12 Jul 2007 03:44:35 GMT

The .Net patch of July 10th, ms07-049 http://www.microsoft.com/technet/security/Bulletin/ms07-040.mspx

.NET 2.0 : Point important concernant le bulletin MS07-040

CoqBlog — Sun, 15 Jul 2007 00:44:40 GMT

Après avoir installer un des patch de juillet ( KB928365 du bulletin MS07-040 ), il est possible que

re: Vista changes .Net 2.0 Locale Names, sample work around custom cultures/locales

NotFooled — Tue, 17 Jul 2007 06:20:00 GMT

Microsoft fails to mention that the MakeCultures.cs workaround only helps if the person already has installed the problem causing security patch. It does no good otherwise. Maybe Microsoft should re-release the security patch with this fix wrapped in so us application developers don't need to deal with the pain and deploy these patches to complaining customers throughout the world. Get a clue Microsoft.

re: Vista changes .Net 2.0 Locale Names, sample work around custom cultures/locales

shawnste — Mon, 23 Jul 2007 23:47:13 GMT

It is worth noting that it doesn't "fix" all cases. Most applications don't have any problems, but for those that do this fix helps many of them. Other users may need to switch which culture is the parent of the other to get resources to load as expected, and some applications may have subtler dependencies that neither technique would address. Unfortunately these and other issues make it difficult to build in an appropriate workaround.