[Announcement] ODataLib 6.1.0 release


Hi all,

As our commitment in rolling out new functionality in the OData V4 protocol continuously, we are excited to announce that OData Core Libraries 6.1 has been released to NuGet.  This release contains four packages, Core, EDM, Spatial and the .Net client.

Call to Action

If your team has an existing OData service or is considering adding an OData service, now is an excellent time to engage with us. In addition to building OData stacks, part of our charter is to help Microsoft align behind the OData protocol. If you need input on whether OData can do what your service needs to do, or input on what version of OData you should implement, please feel free to reach out to us at odatafeedback@microsoft.com.

Release Notes

Bug fixes:

  • Fixed a bug for not adding OData-Version header automatically for IODataResponseMessage.
  • Fixed a bug for duplicate function-import element in ServiceDocument if a function is overloaded.
  • Improved the JSON serialization performance for Edm.Binary type.

New Features:

  • ODataUriParser supports new query option $search.
  • ODataUriParser supports $count, $filter, $top, $levels, $orderby, $search and $skip in expand.
  • EdmLib supports adding Core.Description and Core.OptimisticConcurrencyControl annotation through API directly. 

Thanks,

The OData Team


Comments (7)

  1. rjperes says:

    But current version Microsoft.Data.Services.Client in NuGet still targets OData 3, right? When can we expect a new package?

  2. Yi Ding MSFT says:

    @Ricardo Peres Sat, Mar 22 2014 5:19 PM

    A new package is already available. It's the Microsoft.OData.Client package which comes from the old code base so the APIs are pretty much the same as the ones of the Microsoft.Data.Services.Client. For consuming OData V4 services we would recommend that you move to the new package.

    However, the new package only supports V4 so if your client need to consume both V1-3 and V4 services you need to have both packages in your application.

  3. Stephen says:

    @Yi Ding MSF – Is Wcf Data Services going to support V4 of OData?

  4. Bernhard says:

    I am using WCF data service server and client for my project and since i use EF 6.0 as backand, i really like to use V4 and the enum support…

    2 major issues prevent me from doing so:

    – Filtering based on an enum property causes exceptions since client expands the $filter statement into a cast to an interger instead of using the string representation (Namespace.Type'Value').

    – Exception in client when using batches (SaveChangesOptions.BatchWithSingleChangeset).

    Tt works on my server but the client failed to interpret the result.

    For testing purpose, i implemented a small server using the odata WebApi 2.2 beta.

    Are there any informations regarding those 2 issues?

  5. Thiago Rios says:

    I am using WCF DS w/ oData v3 too and I can't upgraded it to v4.

    Yesterday was posted this article. Who is the same scenario, read it:

    http://www.infoq.com/…/asp-net-odata-4

  6. Bernhard says:

    Second test, using a silverlight 5 (out of browser) client:

    – Client crashes at DataServiceQuery.EndExecute with an ArgumentException.

     (stack trace @ Microsoft.OData.Client.BaseAsyncResult.EndExecute…)

    Funny detail: same code in console application (not async of course) works fine…

    I wonder if anyone ever tested the silverlight implementation…

  7. Abhilasha says:

    what changes required to develop Odata V4 data services? only libraries changes?

    Please suggest