The Azure Table service exposes a RESTful interface in which an entity is represented in various formats. Initially, there was only the Atom format to support JSON in recent years. In saving an instance to a table, the Azure Storage library serializes the instance into the appropriate format before invoking the appropriate REST operation on the Table service. Similarly, when retrieving an entity from a table, the Storage Client library deserializes the entry into an instance of the model class.

The Table service supports a limited set of simple datatypes for the properties of entities. These datatypes are listed in the Inserting, updating, deleting, and querying data against the Table Service recipe. By default, the Storage Client library serializes an instance of a model class by converting each public property of one of the supported datatypes into an element in a result entry. Deserialization simply reverses this process.

Method1 and Method2 differ dramatically...