|
Xml
|
The XmlSchemaExportT type exposes the following members.
Methods
| Name | Description | |
|---|---|---|
|
Export | Exports the object to XML |
|
|
FixOversizedStrings | Before serializing your object to XML, all of its string fields are modified to fit. Essentially truncated. This modifies your exported object straight. This includes also string lists. The detection is based on the generated class, you need to have it add the StringLengthAttribute annotations to the fields. Only maximum string lengths are checked against, the minimums are left alone. |
|
|
GetXmlReaderSchemaResolver | Where are your schemas at? Also DTDs, all that stuff |
|
|
GetXmlReaderSettings | Gets settings for the XML reader that is used in validating the import/export XML |
|
|
GetXmlWriter | You can override the default XmlWriter implementation by overriding this and providing your own writer instance |
|
|
GetXmlWriterSettings | You preferred settings for exporting the object to XML. Important, such as the encoding |
|
|
OnPostWrite | Gives you an access to the stream AFTER the object was serialized to the stream |
|
|
OnPreWrite | Gives you an access to the stream BEFORE the object is serialized to the stream |
|
|
PopulateXmlReaderSchemas | Add your schemas to the schema set. To be be used in validation. By default we do follow the schemas declared in the XML |
|
|
ProcessStringLengthConstraints | Checks all filled fields that they conform to the structure. The max string lengths only. Trims the strings from the end if they are too big for the field. You can call this after you have populated your model |
|
ToXmlDateTime | Makes sure date time is converted as valid XML dateTime. This is a well know problem in .Net XML serialization business. This is maybe the easiest fix but rather manual as well. When you know that a type is dateTime in XML, you should pass the date through this. This will strip the parts of second from the date to avoid them to be written. |
|
|
Validate |
See Also