I just blogged about my MIX talk and about various Dynamic Data changes that are around the corner.  Feel free to follow up with questions and comments (on the blog post, or preferably here in the forums).

thanks,
David

I'm hoping the validation attributes from Dynamic Data can be reused in other areas of an application - in particular, how easy/hard do you think it would be to implement both IDataErrorInfo and an IsValid() method to - in my case - tap into these attributes from any MVC controller using the model.

My other thought is could you see other uses for these buddy metadata classes eg. custom serialization attributes etc. Again to make them an integral part of a more complex application/model? So almost as companion POCO/Data Transfer objects to compliment LINQ to SQL entities? Even to use with other ORMappers too.

The validation attributes will absolutely be usable outside of Dynamic Data.  In fact, they live in their own assembly (System.ComponentModel.DataAnnotations.dll), while most of Dynamic Data lives in System.Web.DynamicData.dll.

The buddy class can potentially be used to add arbitrary metadata attributes.  In a sense, it's no different from putting attributes on the true properties themselves, except that the partial class model currently doesn't allow it.  We're really just using the buddy class as a substitute, until the language allows us to put it directly on the property.

David