The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I do't think I really get the point...
Why not a MongoDB store and use JsonConvert.Deserialize<someclass>(json) and JsonConvert.Serialize(someObject)?
If you want all that flexibility you could use Deserialize<dynamic> or even use ExpandoObjects.
I think you forgot a return statement there
honey the codewitch wrote:
// we need the actual base hashcode, not the one// computed by the JsonObject.var jo = Json as JsonObject; // should always be but it doesn't *have* to beif(null!=jo)
I've already rewritten my JSON engine a couple of times, and I've rewritten my TMDB api twice now. That last one made me want to drink. It's huge.
The first go round i guess was me getting the design straight. I needed to do it, so it wasn't a total loss. Massaging the data from TMDb gets ugly sometimes, so i needed something a bit more flexible on the second go, plus i happened on A Better Way(TM) in the process so that's happy.
Anyway, I love using Json to back the state in my entities. It's a joy to code against. Everything is easy, especially given the realm of data interchange
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.