Migrating Data Odata To Odata Core

Microsoft.Data.OData to Microsoft.OData.Core Migration

Overview

Migrate projects from the OData v1–v3 serialization library (Microsoft.Data.OData) to the OData v4 library (Microsoft.OData.Core). Beyond the namespace rename, this migration involves significant type renames (e.g., ODataEntry → ODataResource) and updated reader/writer APIs with async support.

Related skills: migrating-data-edm-to-odata, migrating-data-services-client

Package Reference Changes

Old Reference (Remove)

<PackageReference Include="Microsoft.Data.OData" Version="5.*" />

New Reference (Add)

<PackageReference Include="Microsoft.OData.Core" Version="{latest-stable-version}" />

Use tools or NuGet to find the latest stable version. The Microsoft.OData.Core package depends on Microsoft.OData.Edm — if the project also references Microsoft.Data.Edm, apply the migrating-data-edm-to-odata skill first.

Workflow

Migration Progress:
- [ ] Step 1: Detect Microsoft.Data.OData usage
- [ ] Step 2: Update package references
- [ ] Step 3: Update namespace declarations
- [ ] Step 4: Rename types
- [ ] Step 5: Update reader/writer patterns
- [ ] Step 6: Update batch operations
- [ ] Step 7: Build and verify

Step 1: Detect Microsoft.Data.OData Usage

Scan the project for:

• using Microsoft.Data.OData; and sub-namespace imports
• Types such as ODataMessageReader, ODataMessageWriter, ODataEntry, ODataFeed, ODataBatchReader
• Package reference to Microsoft.Data.OData in the project file

If the project already references Microsoft.OData.Core, no migration is needed.

Step 2: Update Package References

In the project file, replace the old package reference with the new one (see "Package Reference Changes" above). If the project uses centralized package management (Directory.Packages.props), update the version there instead.

Step 3: Update Namespace Declarations

Replace all namespace references:

The v4 library uses Microsoft.OData as the root namespace (not Microsoft.OData.Core). The package name and the namespace differ.

Step 4: Rename Types

These core types were renamed to align with OData v4 terminology:

Step 5: Update Reader/Writer Patterns

The reader/writer APIs gained async overloads and changed method names:

// Old (v1-v3) — reading an entry
ODataReader reader = messageReader.CreateODataEntryReader();
while (reader.Read())
{
    if (reader.State == ODataReaderState.EntryEnd)
    {
        ODataEntry entry = (ODataEntry)reader.Item;
    }
}

// New (v4) — reading a resource
ODataReader reader = messageReader.CreateODataResourceReader();
while (reader.Read())
{
    if (reader.State == ODataReaderState.ResourceEnd)
    {
        ODataResource resource = (ODataResource)reader.Item;
    }
}

Key method renames:

• CreateODataEntryReader() → CreateODataResourceReader()
• CreateODataFeedReader() → CreateODataResourceSetReader()
• CreateODataEntryWriter() → CreateODataResourceWriter()
• CreateODataFeedWriter() → CreateODataResourceSetWriter()

For async code, use the Async suffixed variants (e.g., CreateODataResourceReaderAsync()).

Step 6: Update Batch Operations

// Old (v1-v3)
ODataBatchReader batchReader = messageReader.CreateODataBatchReader();

// New (v4) — synchronous
ODataBatchReader batchReader = messageReader.CreateODataBatchReader();

// New (v4) — async (preferred)
ODataBatchReader batchReader = await messageReader.CreateODataBatchReaderAsync();

The batch reader state enum values are the same, but prefer the async API for new code. The v4 batch format uses the multipart/mixed or JSON batch format depending on configuration.

Step 7: Build and Verify

1. Build the project:

   dotnet build
   

2. Resolve remaining compilation errors — most will be type renames and namespace changes
3. Run existing tests to verify serialization/deserialization behavior
4. If the project serves OData endpoints, verify that clients can still read responses (v4 payload format differs from v3)

Troubleshooting

Atom Format References

OData v4 dropped Atom (XML) format support. If the project uses ODataFormat.Atom or Atom-specific serialization, switch to JSON format. The v4 library defaults to JSON.

Missing CreateODataEntryReader Method

This method was renamed to CreateODataResourceReader(). Update all call sites and the corresponding state checks (e.g., ODataReaderState.EntryEnd → ODataReaderState.ResourceEnd).

Payload Compatibility with v3 Clients

The v4 serialization format differs from v3. If backward compatibility is required, consider running both v3 and v4 endpoints during a transition period. The ODataMessageWriterSettings class controls format options.