There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
Deserialization reliance on GetHashCode
Deserialization makes use of GetHashCode. However, some GetHashCode implementations (wrongly) expect that various references are not null (for example string fields). This leads to null exceptions, which is a serious issue.
It would be nice to have a workaround, maybe a setting to control what happens? For example, presume such instances are unique (I emulated this by substituting Guid.NewGuid().GetHashCode()). On the other hand, GetHashCode cannot guarantee uniqueness since it
is limited to an int result. So there may be a more fundamental issue in play.