(sorry for my poor english)
I am developing a application using WPF, EF Code First using MVVM (Caliburn.Micro).
It should be used mostly to CRUD work. I created a
BaseViewModel<T> class from wich all other ViewModels inherit and exposed a
T Selected property to bind to the View. I know it is not recomended to expose a Model to the View but it just make things simple to get the app running.
Problem is I do not want to pollute my Models (EF POCO classes) with
IEditableObject, etc... So, there is something that I can do here or do I have to really duplicate all Model properties to the ViewModel and give up trying to bind the model directly? I would like to use the attribute validation too, since all models have them already.
I used this approach on the past with Silverlight/RIA but in this case RIA Services generated the classes for me, with all the plumbing code.
I can get the validation errros using Validator class but I also need to indicate the component that has the error no the UI and I think I need to implement
IDataErrorInfo on my model for this to happen, right?
INotifyPropertyChanged I can use something like NotifyPropertyWeaver but my problem is
IEditableObject and something to be able to use the attribute validation.
It would be nice something like
MagicBusinessBaseClassThatImplementAllThoseInterfaces<Model> to encapsulate the model so I can just bind it and move on.
I know I can make this work implementing manually the interfaces on each VM - but just think on all the "duplicated" code make me cringe :(
How WPF developers are doing those kind of things today? There some secret ninja technique that I am not aware of?