Culture code breaking change between .Net framework 2.0 and 3.0 RRS feed

  • Question

  • User-1945523706 posted


    Moving my dev environment to a Vista machine I'm struggling with an issue related to culture code changes in the .Net Framework.

    The application presents software localization data and uses CultureInfo for building language objects. Now, some of the culture codes have changed between 2.0 and 3.0 of the .Net framework, one example is sr-sp-latn that is changed to sr-latn-sp and that's fine. But, running the application on a Vista machine results in an error that "Culture name 'sr-latn-sp' is not supported." when creating a CultureInfo object using sr-latn-sp.

    This happens both running under the local Web Development server (file based web) and through IIS 7. Moving the app over to an XP or Windows Server 2003 machine the application runs fine.
    Application pool in IIS 7 is set to use .Net framework 2.0 as defined by default.

    Anyone has an idea of how you would be able to run the application under Vista without changing the culture codes (or manage them with custom cultures)?



    Tuesday, November 21, 2006 6:24 PM

All replies

  • User1347187933 posted


    This is because of the difference language tag between RFC1766, RFC3066.



    Wednesday, November 29, 2006 2:38 AM