Entity Framework with RIA services, Silverlight - a compromise between denouement and rapid development

Question

I’ve been playing with Entity Framework, WCF RIA Services and Silverlight 4 recently. I’m impressed with how quickly you can develop an application using these tools and you get a lot of “for free”, for example, the Silverlight user interface will automatically learn about some checks that included as DataAnnotations on the EF model. However, it seems that in a large application, it would be undesirable to have a dependency on EF, which is fully promoted throughout the application, including business logic and user interface.

I know that you can use POCO / IPOCO with the Entity Framework, and this is definitely an option for me. However, if you go this route, you lose some “automatic” things, such as Silverlight, that can demonstrate model validation without any extra work.

How do people deal with this? Do you give up some power and put interfaces between different layers to separate other layers from EF? Or do you refuse the denouement to ensure faster development? Is there any way to get my cake and eat it too that I don’t see?

Answer 1

. , . , , , , - . , , ( ) .

, , EF . . , EF , , EF . , - EF. Interceptors, . , , , .

, EF, . , - DataReaders, . WCF ( RESTful) .

. , , , .