Breaking change to CamelCasePropertyNamesContractResolver in 4.0r2

Jun 24, 2011 at 6:29 PM
Edited Jun 24, 2011 at 9:01 PM

I'm finally upgrading from 4.0r1 to 4.0r2. Your release notes for 4.0r2 mention:

  Change - CamelCasePropertyNamesContractResolver updates dictionary and dynamic property names

This change is breaking our code, as we serialize Dictionary<string, Widget> and use case-sensitive matching on that dictionary. I don't really think of the keys of a Dictionary<string, T> as being "property names". I don't suppose there is an easy way to make the new behavior optional?

(Workaround attached to issue http://json.codeplex.com/workitem/20923)

- Ed

Aug 1, 2011 at 5:44 PM

By design: http://json.codeplex.com/workitem/20923