Linq submitchanges not updating
Linq submitchanges not updating joe jonas and zac efron dating
I'm not 100% sure about LINQ but i would say that the seperation is based on transaction control.
You apply any number of updates, inserts or deletes.
The idea is that you have wrapper methods for CRUD (and all other data access) in the business layer so you'd write code like this: True this doesn't look much different than using the LINQ objects directly but the big difference is that you get some level of abstraction for the load and update code so you can inject things like tracing and error handling etc.
So to implement you might use code like this for the Load: and another routine later on that saves this object (assuming that possibly the context has gone away).
That's fine if you use LINQ directly in your UI code but it's not all that great if you use LINQ in the middle tier.