Microsoft onAugust 30, 2024announced the release of the Core OData 9 package. This new package aligns Core with the .NET 8 OData library, changing the internal details of data encoding in the OData format to be more consistent with theOData specification。
Earlier in August 2024, MicrosoftUpdate OData .NET library to version 8.0.0NET Framework. One of the most important changes is the dropping of support for older versions of the . From this release, only .NET 8 and later will be supported. Developers using older versions of the .NET Framework will still be able to use versions of the OData libraries which areRemain actively supported until March 2025, at which time they will be in maintenance mode.
OData 8 library uses new JSON writer.Utf8JsonWriterto serialize and deserialize JSON loads, this new writer is more efficient than the oldJsonWriterfaster and requires less memory. And requires less memory by created because it is not based on theJsonWriter Instead, it is based on TextWriter . While the new writer has been available since OData version 7.12.2, it is now the default implementation in OData 8.
If desired, developers can still use the old writer by calling the AddOData method in the Service Builder and providing an instance that corresponds to the old writer, which has been renamed for clarity.
builder.Services.AddControllers().AddOData(options => options.EnableQueryFeatures().AddRouteComponents(routePrefix: string.Empty, model: modelBuilder.GetEdmModel(), configureServices: (services) => { services.AddScoped < Microsoft.OData.Json.IJsonWriterFactory > (sp => new Microsoft.OData.Json.ODataJsonWriterFactory()); }));
The new writer serializes differently than the old writer. It does not encode all high ASCII Unicode characters as older writers did. For example, it does not encode non-Latin symbols (such as Greek letters) as Unicode number sequences. Instead, it outputs the Unicode characters themselves. The old writer would encode almost all non-ASCII characters as numbers, resulting in a larger payload size and a slower encoding process. The new JSON writer outputs uppercase Unicode characters instead of the lowercase used in previous versions.
Another major change in Core OData 9 is the way dependency injection works; the updated library uses the same abstractions as .IServiceProvider。
builder.Services.AddControllers().AddOData(options => options.EnableQueryFeatures().AddRouteComponents(routePrefix: string.Empty, model: modelBuilder.GetEdmModel(), configureServices: (services) => { services.AddDefaultODataServices(odataVersion: Microsoft.OData.ODataVersion.V4, configureReaderAction: (messageReaderSettings) => { // Relevant changes to the ODataMessageReaderSettings instance here }, configureWriterAction: (messageWriterSettings) => { // Relevant changes to the ODataMessageWriterSettings instance here }, configureUriParserAction: (uriParserSettings) => { // // Relevant changes to the ODataUriParserSettings instance here }); }));
In addition, the new library removes old implementations and standards such as the JSONP format. The new Core OData 9 library is available asNuGet PackageDistribution.OData is available through a variety of NuGet packages, including:
- 8.0.1
- 8.0.1
- 8.0.1
- 8.0.1
The new version has been downloaded 250.000 times in the last 9 weeks. The source code for Core OData is available atAvailable on GitHubThe repository currently has 458 unresolved issues, for a complete list, developers can check out theRelease Notes for the OData 8 .NET Library。