Serialization and Deserialization

Serialization and deserialization are central to how POCO DataSet is used in modern applications. DataSets frequently travel between backend services and UI clients (such as Blazor) as JSON payloads.

JSON Serialization Approach

The serialization model is intentionally simple: POCO objects with predictable structure, no hidden state, and explicit handling of interfaces and concrete types.

• DataSets serialize as ordinary JSON object graphs.
• Tables become collections of rows, with schema stored separately in metadata.
• Interfaces (such as IDataSet, IDataTable, IDataRow) are handled by custom converters that map them to concrete implementations (such as DataSet, DataTable, DataRow).

Round-trip expectations

POCO DataSet is designed for clean JSON round-tripping. A DataSet serialized to JSON and then deserialized back preserves the essential information needed by application logic and UI: table structure, column metadata, and row values.

• Schema and data can travel together when the client needs metadata-driven UI rendering.
• Schema-only payloads can be used when the client needs to build a form without receiving rows.
• Data-only payloads can be used when schema is already known or cached.

What POCO DataSet deliberately avoids

A core goal of POCO DataSet is to keep serialization predictable and free of legacy complexity. For that reason, the model avoids:

• XML-centric serialization patterns and external schema files.
• hidden state machines or implicit relationship propagation.
• code-generated dataset types or designer-driven regeneration workflows.
• circular references that make JSON serialization fragile.

Serializer neutrality

POCO DataSet does not require a specific JSON library. The core idea is the same regardless of serializer: serialize POCO objects, and use explicit converters where interface types must be reconstructed. In practice, this enables predictable behavior with common serializers (for example, System.Text.Json or Newtonsoft.Json) without coupling your application to a single approach.

Where serialization logic belongs

The POCO DataSet core focuses on the data model. Serialization behavior is implemented through serializer-specific packages and converters. This keeps responsibilities clear:

• Core model — defines structure (tables, rows, metadata) without serializer dependencies.
• Serializer layer — provides converters and settings needed to reconstruct interface-based graphs.
• Application — decides payload shape (schema-only, data-only, combined) based on its workflow.

 

Table of Content POCO DataSet Concepts

 

---

Business Process Programming in .Net
© 2004–2026 Laskarzhevsky Software Inc.
Unless otherwise noted, the content of this website is licensed under the Creative Commons Attribution 4.0 International License (CC BY 4.0).
Code examples are provided under the MIT License.
You are free to share and adapt the material provided that appropriate credit is given and any modifications are clearly indicated.
The information provided on this website is for educational purposes only.
The author and publisher make no warranties regarding the completeness or suitability of the information and are not responsible for any damages resulting from its use.