start URI for infoset '{0}'.
'No corresponding start element is open.
&
No matching start tag for end element.
<
An internal error has occurred. DataContract cache overflow.
<
There was an error checking start element of object {0}. {1}
(Start element '{0}' expected. Found {1}.
,Non-empty start element expected. Found {0}.
0MIME writer cannot start preface in '{0}' state.
2Non-empty start element '{0}' expected. Found {1}.
2There was an error serializing the object {0}. {1}
4There was an error deserializing the object {0}. {1}
5Start element '{0}' does not match end element '{1}'.
6MIME writer cannot start new MIME part in state '{0}'.
9There was an error writing end element of object {0}. {1}
There was an error writing start element of object {0}. {1}
=Start element '{0}' from namespace '{1}' expected. Found {2}.
?An internal error has occurred. Overflow on MIME writer buffer.
An internal error has occurred. Object table overflow. This could be caused by serializing or deserializing extremely large object graphs.
BAn internal error has occurred. Data can only be stored into ArgBuilder or LocalBuilder. Got: {0}.
CWriteState '{0}' not valid. Caller must write start element before serializing in contentOnly mode.
Error in line {0} position {1}.
Error on schema export
Error on schema import
FError while getting known types for Type '{0}'. The type must not be an open or partial generic class.
GNon-empty start element '{0}' from namespace '{1}' expected. Found {2}.
KAn internal error has occurred. ExtensionDataReader is in an invalid state.
MAn internal error has occurred. '{0}' is not assignable from '{1}' - error generating code for serialization.
MAn internal error has occurred. No conversion is possible to '{0}' - error generating code for serialization.
MWriteStartElement can be called at only the start of a document or immediately after calling WriteEndElement.
RAn internal error has occurred. Char is not a valid schema primitive and should be treated as int in DataContract.
TAn internal error has occurred. Could not load serialization schema. Consider providing schema with namespace '{0}'.
The 'maximum bytes per Read operation' quota ({0}) has been exceeded while reading XML data. Long element start tags (consisting of the element name, attribute names and attribute values) may trigger this quota. This quota may be increased by changing the MaxBytesPerRead property on the XmlDictionaryReaderQuotas object used when creating the XML reader.
The type '{0}' cannot be serialized to JSON because its IsReference setting is '{1}'. The JSON format does not support references because there is no standardized format for representing references. To enable serialization, disable the IsReference setting on the type or an appropriate parent class of the type.
YDateTime content '{0}' does not start with '{1}' and end with '{2}' as required for JSON.
[An internal error has occurred. Unexpected contract type '{0}' for type '{1}' encountered.