[Announcement] ODataLib 6.8.0 Release

We are happy to announce that the ODataLib 6.8.0 is released. Detailed release notes are listed below.

Bug Fix

  • Remove the ordering constraint in ODataLib which forces instance annotations of a property to come before the property in complex value
  • Fix a race condition issue for finding navigation targets in EdmLib.

New Features

  • EdmLib supports edm:EnumMember Expression for metadata annotations.

  • EdmLib & ODataLib now support TimeOfDay and Date.

  • ODataLib supports reading and writing entities as parameter.

  • ODataUriParser supports two new built-in functions: time and date.

  • ODataUriParser supports overriding default behavior for resolving unbound operation name in query options.


Call to Action

You and your team are highly welcomed to try out this new version if you are interested in the new features and fixes above. For any feature request, issue or idea please feel free to reach out to us at odatafeedback@microsoft.com.

Comments (6)

  1. Mike says:

    Great, but can you pleas stop putting acronyms on top of acronyms Microsoft???  Odata is a partial acronym already!  ODL is just overkill…. Typical Microsoft

  2. Samil Lee says:

    I gave up to use/upgrade to OData V4 because of EF datatype datetime not supported.

    I had no choice for my MySQL.

    So, is the datetime  supported now like in V3?

  3. Layla Liu says:

    @Mike, Thanks for your suggestion.

  4. Vagif Abilov says:

    I have updated OData libraries from version 6.7.0 to 6.8.0. Now it no longer manages to read schema documents if a mode contain Enum members. A simple test is a TripPin OData service available at odata.org: its model can no longer be read by the ODataLib libraries. I have example test code, but it should be no brainer to reproduce it: just try calling ReadMetadataDocument for TripPin OData V4 service.

  5. Jordi Scharloo says:

    Appears not, Samil Lee. I myself am also unable to use MySQL as of V4.

  6. Stephen says:

    @Samil Lee @Jordi Scharloo – This is a critical mistake by the designers of OData.  But it looks like the Web API team is going to make it right in their implementation.

    This work item (aspnetwebstack.codeplex.com/…/2072) indicates that DateTime support is planned for the next iteration release (5.4).

Skip to main content