The Open Data Protocol (OData) has rapidly gained popularity as an efficient way of exposing data sources via REST services. Platform neutrality of the protocol makes it a great choice when developing both data services and clients, and with Visual Studio 2010 and .NET 4.0 tools and libraries adding OData support to a data repository can be as easy as subclassing a generic type. Default implementation of OData services generated with Visual Studio is concise and powerful, but in this session we will consider scenarios when default is not enough. Canonical RESTful service should conform to certain rules, does your OData service obey them? How can you expose a conceptual data model shared by databases from different vendors, for example Microsoft SQL Server and Oracle? What does it take to replace Entity Framework with NHibernate? And how to capture errors, so exceptions raised from a data layer will not be buried by standard WCF exception handlers?
Download this video from http://ndc2011.macsimum.no/mp4/Day1%20Wednesday/Track6%201740-1840.mp4