Does anyone know of blog posts, forum posts, books, videos, or anything that offers a good example of the following:
An ASP.NET web application consuming a WCF service which hosts an Entity Framework model with both a Domain Service and Entities of course.
I have had no problem with this model if I put everything (model, domain service) in one asp.net project, but I want to make a 2-tier model.
I have been searching endlessly and have not found anything which details how this can actually be accomplished with using the standard Entity Model/Domain Service architecture, and accessing this from a separate tier (asp.net application). When I add a Service
to the ASP.NET web app which points to the WCF Data service, I do not have access to my Domain Service methods (CRUD), and my entities.
Again, works great in one project, and all of the samples show a one project solution. What about a real n-tier solution for this model?
Thanks to anyone who can offer good guidance on this topic.
View Complete Post