6 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Rafael L commented  ·  February 15, 2012 9:28 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  WFC Data Service should suport this kind of modeling.

• Jorge Ortiz commented  ·  June 23, 2011 11:16 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

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

• DotNetWise commented  ·  June 13, 2011 4:55 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

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

• Marcel Šerý commented  ·  December 2, 2010 4:28 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is really an essential functionality for enterprise modelling.

• francesco leonetti commented  ·  December 1, 2010 10:26 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  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 Haltom commented  ·  September 23, 2010 10:37 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  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.