GetClosestMatchProperty makes deserialization of backingfield with getter fail about newtonsoft.json

[asgerhallas]

Ok, it does not look like it has anything to do with GetClosestMatchProperty()... Hmm... I'm investegting further, it looks like two different, but similar behaviours I've encountered.

[asgerhallas]

Ok. I've encountered two different issues.

The Second issue is actually related to GetClosestMatchProperty, when you have a json document with a property that is no longer present in the new representation of the .net class (migrating documents from a Raven database).

The test for this is:

[TestFixture]
public class FallbackToCaseInsensitiveFailsForThisCaseTest
{
    [Test]
    public void CanDeserializeFromJsonWhereTwoPropertyAreSimilarlyNamed()
    {
        var settings = new JsonSerializerSettings
                                         {
                                             ContractResolver = new PrivatesOnly(), 
                                             TypeNameHandling = TypeNameHandling.All
                                         };

        JsonConvert.DeserializeObject<SomethingWithAList>(
        @"
        {      
        ""ints"": {
                  ""$id"": ""469"",
                  ""$type"": ""System.Collections.Generic.List`1[[System.Int32, mscorlib]], mscorlib"",
                  ""$values"": []
                },
                ""Ints"": {
                  ""$id"": ""470"",
                  ""$type"": ""System.Int32[], mscorlib"",
                  ""$values"": []
                }
        }
        ", settings);
    }

    public class PrivatesOnly : DefaultContractResolver
    {
        public PrivatesOnly()
            : base(false)
        {
            DefaultMembersSearchFlags = BindingFlags.Instance | BindingFlags.NonPublic;
        }
    }

    public class SomethingWithAList
    {
        readonly List<int> ints = new List<int>();
        public IEnumerable<int> Ints
        {
            get { return ints.Where(x => x > 10); }
        }
    }
}

Would you like a pull request with the failing tests? Or is here ok?

[asgerhallas]

If you even consider them bugs, that is :)

The first one seems to be solvable by some settings - when I get the serializer through RavenDb the issue goes away. But I can't figure out why.

The second one is happening, because I try to deserialize with another contract resolver than I serialized with, so it might not be such a valid case. But it would still be nice to be able to disable the fallback to case insensitive properties and just ignore if a property is missing.

[JamesNK]

I believe you could override this by creating your own contract resolver.

[andresmoschini]

@asgerhallas did you implement your own contract resolver? (I need case sensitive deserialization)