When I started using xVal I was mostly implementing action methods which used domain model objects as a viewmodel. This approach works fine most of the time, but there are cases when I need a viewmodel which contains only a subset of the model's properties.
The only workaround I have found for that scenario is creating a custom viewmodel containing those properties and adding validation attributes to the viewmodel itself.
This approach works, but it's far from perfect since I have to repeat the same validation attributes that are already present on the domain model object.
The buddy class technique doesn't help here since xVal throws when the metadata class has properties that are not present on the viewmodel.
Is there any elegant workaround to this?