Created Entity Framework 4.0 vs POCO Entity Set with INotifyPropertyChanged / IDataErrorInfo

Question

suggests that I am creating entities and I need data binding + error checking in wpf with the mvvm template. Where is the Poco promotion? POCO is naked and has nothing ... noInotifyPropertyChanged or IDataErrorInfo. Due to the very hard work, I do not wrap my objects, such as Customer, in CustomerVM / CustomesVM (collection), etc. .... I return my data to List <> passed it the ObservableCollection constructor and attached to this collection from the view . Easy and less code.

So why should I use POCO, which is an excellent feature in EF 4.0, so they say ...

Answer 1

I myself study this new material, but still think the story goes like this: POCO classes are deployed (under the hood) to their equivalent EF classes that already support Propertychanged notification.