Allow re-using entities from another dll on the client-side generated code
When adding a service reference to a WCF Data Service allow me to choose a project or dll which has the entities already defined as POCOs which can be used (using their original namespaces) rather than re-creating the entities in the Reference.cs with the same namespace as the service.
This should make things much easier on a large scale project with multiple WCF Data Services which all use the same EF entities.
John Crim commented
This is possible with some effort. I was able to get this to work by reverse-engineering the generated client code. I haven't found much documentation on this, so I'll probably do a blog post on it.
The short version is that you need to subclass DataServiceContext (like the client generator does for you), and then override ResolveTypeFromName() and ResolveNameFromType() so they map your class namespaces to the Edm namespace. I've provided a little more info with this answer on stack overflow: http://stackoverflow.com/questions/6371243/wcf-dataservices-ctp2-there-is-a-type-mismatch-between-the-client-and-the-ser/14721900#14721900
Also this should make client-side entities implement the same interfaces/base-classes as server-side do, should it not?