<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Odata on Strathweb. A free flowing tech monologue.</title>
    <link>https://www.strathweb.com/categories/odata/</link>
    <description>Recent content in Odata on Strathweb. A free flowing tech monologue.</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 18 Feb 2014 12:38:05 +0000</lastBuildDate><atom:link href="https://www.strathweb.com/categories/odata/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Getting started with OData v4 in ASP.NET Web API</title>
      <link>https://www.strathweb.com/2014/02/getting-started-odata-v4-asp-net-web-api/</link>
      <pubDate>Tue, 18 Feb 2014 12:38:05 +0000</pubDate>
      
      <guid>https://www.strathweb.com/2014/02/getting-started-odata-v4-asp-net-web-api/</guid>
      <description>&lt;p&gt;Since yesterday, the ASP.NET Web stack nightly feed contains the packages supporting OData v4. The package is called &lt;em&gt;Microsoft.AspNet.OData&lt;/em&gt; and has a working version 5.2.0 - so I&amp;rsquo;m guessing this is intended to ship with Web API 2.&lt;/p&gt;
&lt;p&gt;It relies on the latest beta of &lt;em&gt;Microsoft.OData.Core&lt;/em&gt;. OData v4 is a massive changed compared to v3 - you can read about all of them [here][1].&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Easy ASP.NET Web API resource updates with Delta</title>
      <link>https://www.strathweb.com/2013/01/easy-asp-net-web-api-resource-updates-with-delta/</link>
      <pubDate>Fri, 11 Jan 2013 15:23:54 +0000</pubDate>
      
      <guid>https://www.strathweb.com/2013/01/easy-asp-net-web-api-resource-updates-with-delta/</guid>
      <description>&lt;p&gt;One of the great features of the &lt;em&gt;Microsoft ASP.NET WebAPI OData&lt;/em&gt; package (which you can grab as prerelease from Nuget, and which will soon, in next release cycle, become part of Web API core) is a little dynamic proxy object called &lt;em&gt;Delta&lt;T&gt;&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;It allows you to perform ridiculously easy mapping of properties between the model obtained from the database and the model passed by the client - thus facilitating all kinds of update scenarios your application may encounter.&lt;/p&gt;
&lt;p&gt;Unfortunately, it will not work for you - unless you commit to &lt;em&gt;ODataMediaTypeFormatter&lt;/em&gt; and all the extravaganza related to OData. What if you want to use the traditional API formatters, but still leverage on the power of &lt;em&gt;Delta&lt;T&gt;&lt;/em&gt;?&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s have a look at how you can perform really smooth full (PUT) and partial (PATCH) updates of your resources in Web API.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Supporting OData $inlinecount with the new Web API OData preview package</title>
      <link>https://www.strathweb.com/2012/08/supporting-odata-inlinecount-with-the-new-web-api-odata-preview-package/</link>
      <pubDate>Thu, 23 Aug 2012 11:43:02 +0000</pubDate>
      
      <guid>https://www.strathweb.com/2012/08/supporting-odata-inlinecount-with-the-new-web-api-odata-preview-package/</guid>
      <description>&lt;p&gt;OData support in Web API is arguably one of its hottest features. However, it&amp;rsquo;s support in Web API has been a bumpy ride - initially, OData was supported in a limited way only, and ultimately ended up being yanked altogether from the Web API RTM. It is however stil lpossible to use OData with Web API, only in a slighly different form , as an [external NuGet package][1], which, in its pre-release alpha format was published last Wednesday, along the Web API RTM release.&lt;/p&gt;
&lt;p&gt;This package is called &lt;strong&gt;Microsoft ASP.NET Web API OData&lt;/strong&gt; and is a joint effort by Microsoft&amp;rsquo;s Web API and OData teams. Alex James has written a [great introduction][2] to the package, so I recommend reading it.&lt;/p&gt;
&lt;p&gt;In the meantime, let me show you how to add $inlinecount support as for the time being, it&amp;rsquo;s still not provided there out of the box.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Extending your ASP.NET Web API responses with useful metadata</title>
      <link>https://www.strathweb.com/2012/06/extending-your-asp-net-web-api-responses-with-useful-metadata/</link>
      <pubDate>Sun, 03 Jun 2012 13:27:13 +0000</pubDate>
      
      <guid>https://www.strathweb.com/2012/06/extending-your-asp-net-web-api-responses-with-useful-metadata/</guid>
      <description>&lt;p&gt;If you ever worked with any API, which, in this day of age, you must have, you surely noticed that in most situations the API response isn&amp;rsquo;t just the result (requested data), but also a set of helpful metadata, like &amp;ldquo;total Results&amp;rdquo;, &amp;ldquo;timestamp&amp;rdquo;, &amp;ldquo;status&amp;rdquo; and so on.&lt;/p&gt;
&lt;p&gt;In Web API, by default, you just serialize your models (or DTO) and such information are not present. Let&amp;rsquo;s build something which will solve this problem and help you decorate your response with hepful information. This would make it very easy for the client to implement paging, auto-loading scenarios, caching (if you return last modified information) and a lot more.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
