locked
OData v3 service from VS 2010 not generating proper Schema element (JayData) RRS feed

  • Question

  • I have a WCF Data Service which is supporting V3 of OData. I can prove this by using the any and all methods when querying but I'm trying to consume this service using JayData and JayData only generates V2 client code. It does so by choosing version based on the namespace of the Schema element that's part of the metadata of the WCF service.

    I am using Visual Studio 2010, WCF Data Services 5.5, and Entity Framework.

    Namespace versions from JayData and OData spec are as follows:

    public static Dictionary<string, string> NamespaceVersions  = new Dictionary<string,string>
      {
        {"http://schemas.microsoft.com/ado/2007/05/edm", "V11" },
        {"http://schemas.microsoft.com/ado/2006/04/edm", "V1" },
        {"http://schemas.microsoft.com/ado/2008/09/edm", "V2" },
        {"http://schemas.microsoft.com/ado/2009/08/edm", "V21" },
        {"http://schemas.microsoft.com/ado/2009/11/edm", "V3" }
      };

    Visual Studio generates the following metadata schema:

    <edmx:Edmx xmlns:edmx="http://schemas.microsoft.com/ado/2007/06/edmx" Version="1.0">
    <edmx:DataServices xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" m:DataServiceVersion="1.0" m:MaxDataServiceVersion="3.0">
    <Schema xmlns="http://schemas.microsoft.com/ado/2008/09/edm"

    How can I correct this namespace so clients can properly consume the service that rely on this namespace?

    Tuesday, July 2, 2013 1:39 PM