Fluent-API based metadata (to replace buddy classes)
Prototype/description at http://www.nikhilk.net/RIA-Services-Fluent-Metadata-API.aspx
I am working on an application using RIA Services, this application has different user groups and each group has its own set of required fields and valdiations. So the metadata has to be dynamic in the application. Is it completely impossible in RIA to handle this kind of scenario.
K Wood commented
Couldn't this be accomplished if the T4 generation was implemented?
Installation-specific metadata is already supported. You can have whatever source of metadata (see external metadata sample on code gallery).
In the current model, fully dynamic metadata requires a rebuild which is a completely different beast from fluent API. I get why rebuild / dynamic metadata would be interesting but I don't really see the connection to fluent API. It is a different syntactic form for a capability that already exists.
I like this a lot, I hope that this gets the thumbs up and replaces metadata buddy classes everywhere including Dynamic Data and MVC.
Paulo Aboim Pinto commented
This would be just great.
Paulo Aboim Pinto
Odivelas - Portugal
The metadata support is not right; I would like it dynamic, although supporting metadata through a designer should be considered as an option also.
Kathleen Dollard commented
I actually do not care whether the result is fluent or not. I need a system to support dynamic, installation specific and controlled metadata for authorization, validation and display details. I need this to be available on the client, but the rare validation deatil (such as wehther something is a uinique key) to be marked as server specific. I would also like to ensure (haven't actually tried it) that all messages can be localized/bidi.