ValidationContext.MemberName is set incorrectly in the DataAnnotationsModelValidator

[mkArtakMSFT]

Problem Description

My customer creating custom validation class which deliveerd from System.ComponentModel.DataAnnotations.ValidationAttribute.
Using this in .NET4.7.1 ASP.NET Web API 2.0, ValidationContext.MemberName is set "DisplayName".
This is problem for custom class because they can not know MemberName without this property.

• Expected behavior
  ValidationContext.MemberName is "TestValue3"
• Actual behavior
  ValidationContext.MemberName is "Display name From 'DisplayAttribute'"

TestValue3 is set "DisplayAttribute".

    public class TestModel
    {
        [Validations.CustomValidation]
        public string TestValue1 { get; set; }
        [Validations.CustomValidation(ErrorMessage = "ErrorMessage: {0} ErrorMessage")]
        public string TestValue2 { get; set; }
        [Validations.CustomValidation(ErrorMessage = "ErrorMessage: {0} ErrorMessage")]
        [Display(Name = "Display name From 'DisplayAttribute'")]
        public string TestValue3 { get; set; }
        public string Message { get; set; }
    }

[mkArtakMSFT]

@dougbu, please associate the fix we've discussed with this bug. //cc: @danroth27

[dougbu]

For historical interest: Was a PR for this in the old CodePlex repo http://aspnetwebstack.codeplex.com/SourceControl/network/forks/astolfoho/fixWebApi/contribution/8918. But, I can't find an earlier issue on this.

[dougbu]

Moved to 3.2.5 (really 3.2.5-preview1).

[dougbu]

9829dd8

[kraeg75]

I still see this problem.
My Web API references System.Web.Http in the Microsoft.AspNet.WebApi.Core.5.2.4 NuGet package which was published on May 21, 2018. The System.Web.Http dll itself is dated Feb 1.
The 9829dd8 commit above is dated Jan 24, which leads me to believe the dll should include the fix.

[dougbu]

This fix is in MVC 5.2.5 preview 1 and later, not 5.2.4.

FYI the commit date may be much earlier than when the changes are merged into the master branch.