Nice article Shawn. Gives me a nice overview of how Data Services work.

I have some questions:

1. The business logic would go where? Lets say I have an invoice an I want something that validates the supplier. To me, thats not somethign that goes at the back end. By the time it gets there its too late. So would I include that in the partial class that would be generated for the Invoice entity for the OnPropertyChanging event of the supplier?

2. Where would I add code to do BeforeSave type checks? Or to prevent an object from being saved if its not validate?

Thanks

Its not entirely clear the right pattern yet to do this but I am working on some better advice in a new article to discuss business logic coming soon!

I hope its soon! I've not been able to spend a lot of time on this stuff (stuck in maintenance mod on an older system) but have been doing a lot of reading. I have been going around in circles for the last two months trying to find a framework that would suit the way I would like to work. It always seems to be just another article away. I've been hangin out for Karl's Ocean framework as well to get some more ideas.

What I would ideally like is a solution which would be usable in Silverlight or WPF (which I think from your article is doable). I'd also like to be able to have a repository option so that I could get the data from ADO.NET DataServices for remote clients but to be able to go straight to the Entity Framework in a LAN environment, in order to improve performance on large batch jobs that need to work over a lot of entities.

Cheers

I second this. We're writing *way* too much code here what with SQL, DAL and service layers and EF+ADODS looks to be the way (or one way) forward.