I searched first, and basically I am trying to avoid having to use JObject in C# in favor of ANY Serializer. An excerpt of a large Microsoft Dynamics JSON trace has JSON formed like this
{
"InBlockOStuff" :
{
"type":"Yea You Know What this is",
"values":[
{
"Key":"Target",
"Value":{
"type":"Yea You Know What this is",
"LogicalName":"Thangie",
"Id":"GuidAs String",
"MagicalContent":{
"type":"Yea You Know What this is",
"values":[
{
"Key":"firstname",
"Value":"New Test thangie One"
},
{
"Key":"Thangieid",
"Value":"some stupid Guid like thangie"
}
]
},
"Shaggy":null,
"SubCategory":{
"type":"Yea You Know What this is",
"values":[ ]
},
"Velma":{
"type":"Yea You Know What this is",
"values":[ ]
},
"Scoobie":null,
"KeyAttributes":{
"type":"Yea You Know What this is",
"values":[ ]
}
}
},
{
"Key":"some text",
"Value":true
},
{
"Key":"some text",
"Value":0
}
]
}
}
Notice the repeated instances of the "keys" value and values It is valid Json, the online validators say it is legit, the online generators will additionally create C# classes/objects but I'm sure you instantly see this mess will have two distinctly different "Values" classes. And that doesn't serialize cleanly.
So am I stuck having to learn JObject to get my data out of this mess?
This is just high level excerpt there exists, for example another MagicalContent key with a different set of key values inside of it, just for arguments sake.