There is a new CTP out for WCF Data Services (v3), which features the long awaited support for properties on derived types (yay!) You can get it from here.
The following proposed OData version 3.0 functionality is also supported by WCF Data Services in this release:
The following additional functionality is also provided by WCF Data Services in this release:
Does this version support EF code first's DbContext object? Or is the ObjectContext workaround you've shared still needed? Thanks
I haven't seen any improvements made to make it easer to to use a Code First DbContext with WCF Data Services. You can go here to vote to add this as a new feature: data.uservoice.com/.../2360134-support-dbcontext-as-a-ef-provider-context
Also, I created a topic in the TechNet Wiki that describes how to use EF Code First with WCF Data Services: social.technet.microsoft.com/.../5234.aspx
There's an extension library on codeplex that provides access to DbContext and the message body.
That library is interesting, but it is essentially getting the stream (message body) from the OperationContext of a client response (somehow by reflection). It doesn't really have anything to do with Code First DbContext, and doing this doesn't really follow the OData protocol, which doesn't define support for service operation payload for a POST operation (which is why you have to use parameters).