Data annotation localization current culture missmatch

[aspnet-hello]

From @stenvix on Monday, May 22, 2017 1:33:54 AM

Technical details

Operating system: Windows 10
IDE: Visual Studio 2017 Professional Version 15.2(26430.6)
Runtime: .NET Core 1.1

Information

I had strange behaviour when use data annotation with "ResourceType",

Like in docs I init localization:
ConfigureServices

            services.AddLocalization(options => options.ResourcesPath = "Resources");

            services.AddMvc()
                .AddViewLocalization(LanguageViewLocationExpanderFormat.Suffix)
                .AddDataAnnotationsLocalization();

Configure

            var supportedCultures = new List<CultureInfo>
            {
                new CultureInfo("en"),
                new CultureInfo("uk"),
                new CultureInfo("ru")
            };

            app.UseRequestLocalization(new RequestLocalizationOptions
            {
                DefaultRequestCulture = new RequestCulture("en"),
                SupportedCultures = supportedCultures,
                SupportedUICultures = supportedCultures
            });

In model I use attribute

[Display(Name = nameof(RememberMe), ResourceType = typeof(DataAnnotations))]

IHtmlLocalizer, IStringLocalizer working correctly, But name on DataAnnotations use Russian resx by default
English Language:

Link

But if I use Ukrainian language all working fine

Ukrainian Language:

Link

Have any logical explanation why this happend??

Copied from original issue: aspnet/Localization#371

[aspnet-hello]

From @hishamco on Monday, May 22, 2017 3:59:38 AM

@stenvix please refer to this issue #343, if everything as expected, please share a repo that reproduces the issue that you are facing

[aspnet-hello]

From @rynowak on Monday, May 22, 2017 8:11:23 AM

@stenvix can you share your model code? The data annotations attributes have some complicated behavior because they have their own localization system.

[mkArtakMSFT]

Hi. We're closing this issue as we have heard no response from you for some time now. If you have more details and are encountering this issue please add a new reply and re-open the issue.