I have a lot of dropdown lists, custom grids on my webform which are displayed to the end user. Each is populated from database through a DAL. I have separate classes defined for each. However, I am thinking about reducing the number of classes, as every new requirement results in a separate custom object.How can I reduce the no. of classes for such requirements? Should I use datasets, lists etc. ?
Ending with too many objects (layered design)
- Thread starter wamucng
- Start date