Geek Answers Handbook

Is there a design pattern for comprehensive aspnet UI authentication?

As an example, let's say I have an object with one domain with 100 properties. In my user interface, I need a complex style check:

  • If A = 1, show controls B, C, D. B is required, C is not, and D is not required, must be less than 30 if it is full.
  • If A = 2, show controls B, D, E. B is not required, D is required but not limited, and E is not required.
  • If A = 3, display controls B, E, F. B is required and must be greater than 10, E is required, F is not required.
  • If B = 3 and F = 5, then show the control G, but only if A = 3.

Here you can see my problem. The relationships between properties are terribly complex, with validation varying with earlier values ​​and in combination with other values.

How have people modeled and handled this in the past? Validation is not required very often, but a config / xml based solution is likely to be better.

+5
source share
1 answer

You can project this gigantic domain object onto smaller objects that contain only subsets of the required properties and name them according to the script that they describe. It creates some kind of ViewModel if you do.

A = "X" B = "Y" . , ViewModel. ViewModels / .

+1

More articles:


All Articles