1) The frame does a good job of extrapolating data annotations based on the table structure, but they will not be ideal.
2) Unfortunately, when you reach the point where you want to customize more than the framework, you are stuck with the Buddy classes. They are a bit tedious, but so far the best method I have found for setting data annotation.
3) Too often, I find myself attracted to custom classes and from POCO created ones. The reason usually is the difference between storage and display. On input screens
- I often split the phone into 3 text fields.
- Searching for foreign keys requires selection of lists (often added to the model).
- Often I pass in other values ββthat may be relevant to my View function, but not related to the storage table (display fields, navigation / breadcrumbs).
source share