I have a workflow and am persisting it into the database. It all worked fine until I tried using entities in the workflow. Because I\'m using POCOs the workflow seems to have trouble serializing the o
I am using Entity Framework with POCO objects and have the following scenario: I create a new parent object and add a child object to it. Then I save changes and detach the parent object. At this mom
Quick question for all y\'all silverlight buffs.. I need to expose a custom POCO object through ria services.. Well kind of, i could probably get away with doing it over a vanilla web service.. so i
If I am generating POCO objects from EntityFramework, and using these to go to/from the WCF server, is there any reason to create client-side Models for the Views & ViewModels to use instead of ju
Closed. This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this
Which is better implementation or there is no difference? 1. public class Simple { public IList<string> Entries { get; private set; }
What are some questions I can ask myself about our design to identify if we should use DTOs or Self-Tracking Entities in our application?
the LoadProperty is good alternative for Include method... Problem with Eager Loading Nested Navigation Based on Abstract Entity (EF CTP5)
My MVC ASP.NET web application is split up like this: Web Application Layer Views Domain Layer Repository
i am working with Entity Framework 4.1 with POCO. I would like to map table Employees : EmployeeID LastName
加载中,请稍侯......