ayende/ravendb — comment on commit da385ae513a328e34ca1e9640119000b82662786
File:  line 0
By etishor:

Not supporting values or IEnumerables as first class entities sounds reasonable, but maybe the exception can be made more clear for the user if he tries to store such type.

About private fields, maybe by default, at least in debug, check if the serialized object has private fields and force the user to be explicit about them, either by changing the flag of the ContractResolver or some other other flag to specify that private fields should or should not be serialized. This would prevent the user from any wrong assumption about private fields ( i know i assumed they would be serialized by default ).

I totally agree on the issue with concurrent dictionaries, and anyway the issue will resolved when json.net 4.0.4 ( not found :) ) comes out.