by Michael S. Kaplan, published on 2010/04/08 07:01 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2010/04/08/9991592.aspx
The question was one that regular readers might recognize:
I have a customer who’s trying to create CultureInfo for bs-Latn-BA (Bosnian Latin) in a .NET Framework 1.1 application using the below statement:
System.Globalization.CultureInfo c = new System.Globalization.CultureInfo(“bs-Latn-BA”);
They are getting “System.ArgumentException: Culture name bs-Latn-BA is not supported. Parameter name: name”. However, if they try the same thing in .NET Framework 2.0, it works.
The exception message appears clear but I just wanted to make sure that bs-Latn-BA is absolutely not supported (no workaround or anything) in .NET 1.1 before I tell them.
Any ideas, resources, documentations that you can point me to?
Note that they are running this on Windows Server 2003 SP2.
This is that Windows-Only Culture feature, where .Net synthesizes a new CultureInfo from Windows when it can't get the data from its own store (due to it not being there).
There is an MSDN topic that talks about them here, and of course you can check out blogs here by searching for Windows-only cultures if you want to learn way too much about them, more than any normal human would really need.
The most relevant bit to the original question is that this feature was added in .NET 2.0 -- which is why this CultureInfo cannot be created in 1.1.
So version 1.1 isn't old enough if you want to get your Bosnian on....
ekolhoca on 8 Apr 2010 8:06 AM:
go to newer or older post, or back to index or month or day