DisplayNameFor doesn't lookup resx file despite IStringLocalizer and IHtmlLocalizer working correctly in the Razor page

[Duke4848]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I've got my Login.cshtml page

@page
@using Microsoft.AspNetCore.Mvc.Localization
@using Microsoft.Extensions.Localization
@inject IStringLocalizer<LoginModel> localizer
@inject IHtmlLocalizer<LoginModel> htmlLocalizer
@model LoginModel

<h1>@htmlLocalizer["Title"]</h1> TRANSLATES WELL
<h1>@localizer["Title"]</h1> TRANSLATES WELL
[...]
div class="checkbox">
   <label asp-for="Input.RememberMe" class="form-label">
        <input class="form-check-input" asp-for="Input.RememberMe" />
        @Html.DisplayNameFor(m => m.Input.RememberMe) //DOESN'T WORK, DOESN'T LOOKUP RESX FILE
    </label>
</div>

In the scaffolded Login.cshtml.cs page model there is an attribute [Display] fr the RememberMe property, but this one is not getting translated despite translation being put in the same resource file

        /// <summary>
        ///     This API supports the ASP.NET Core Identity default UI infrastructure and is not intended to be used
        ///     directly from your code. This API may change or be removed in future releases.
        /// </summary>
        [Display(Name = "Remember")] //DOESN'T WORK, DOESN'T LOOKUP RESX FILE
        public bool RememberMe { get; set; }

We can see that the structure is correct

Resx file itself:

This is what gets rendered:

Expected Behavior

Remember gets translated according to the contents of the resource file.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

6.0.402

Anything else?

ASP.NET Core 6

[Duke4848]

So at least one of the reasons is the bug I reported: https://developercommunity.visualstudio.com/t/Custom-tool-cant-generate-designer-file/10213747?
The other one is that for some reason I need to provide ResourcesFileType in the attributes despite conforming to the naming conventions.

To learn more about what this message means, what to expect next, and how this issue will be handled you can read our Triage Process document.
We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. Because it's not immediately obvious what is causing this behavior, we would like to keep this around to collect more feedback, which can later help us determine how to handle this. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact work.

[hishamco]

@Duke4848 I remembered there was an issue in DisplayAttribute, could please confirm if it exists with the latest bits?