WCF Data Services Feature Suggestions

Support Navigation Properties on Derived Types

436 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mike FlaskoMike Flasko shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    6 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Jorge OrtizJorge Ortiz commented  ·   ·  Flag as inappropriate

        Almost every merely complex data model includes some inheritance, so, WFC Data Service should suport this kind of modeling.

      • DotNetWiseDotNetWise commented  ·   ·  Flag as inappropriate

        This seems to be sort of implemented in EF 4.1 & WCF Data Services CTP2 as of Apri/June 2011

      • francesco leonettifrancesco leonetti commented  ·   ·  Flag as inappropriate

        Real world domains contain derived types and navigation to derived types. EF DO fully support them; WCF Data Services DON'T: really big shame because this leads to a painful integration process when trying to expose models through OData protocol.

      • Jerome HaltomJerome Haltom commented  ·   ·  Flag as inappropriate

        Yeah. Really. This WCF Data Services thing simply not working with EF sort of sucks. What's worse is there's no way to load this type without the navigation properties, the only work around is to go break your model... which may be shared by other apps. Not cool.

      Feedback and Knowledge Base