ASP.NET C #: which design pattern should I use and why?

Question

I am developing an application in ASP.NET C # and came across the following script:

• I will need to create several maintenance screens for different objects (tables).
• These objects will basically have the same behavior in the user interface: Search, GetById, Save, Create and GetAll
• Entities can have a different structure, that is, different properties (fields)

As I speak of the 20 plus admin screens, which design template could I use to minimize the amount of code I need to write?

Although I’m from a bridge template , but I'm a little confused about how to implement it ...

Some technology that I use:

• ASP.NET classic (n-level)
• LINQ to SQL and DAO Objects
• SQL Server 2005

Answer 1

For a set of admin screens that simply perform CRUD operations (Create, Read, Update, Delete) and with a bit of business logic, I would be very tempted to more or less avoid design patterns and see asp.net dynamic data . This is especially true if you want to minimize the amount of code you want to write.

Answer 2

This is not a design pattern ... but I would strongly suggest using dynamic data. Jonathan Carter has some great articles about this: http://lostintangent.com/index.php?s=dynamic+data

Answer 3

: Search, GetById, Save, Create GetAll, . , , .

, , , , .

, - . , , .

. , . , . LinqToSql, , , , .

.

Answer 4

, . ORM . SubSonic - http://subsonicproject.com. : http://subsonicproject.com/web-forms-controls/the-scaffold/