ASP.NET Patterns

Building websites has been a great attraction and fun to play with for many , though many follow some kind of coding practices without able to reason why we follow such standards in our web development.

The following post helps you to understand the basic ASP.NET patterns that can be followed for building simple - well modularised - easily maintainable Applications.

Basic Design Patterns and Groups
Design patterns fall into groups, based on the type and aims of the pattern.
For example, some patterns provide presentation logic for displaying specific views that make up the user interface. Others control the way that the application behaves as the user interacts with it.

There are also groups of patterns that specify techniques for persisting data, define best practices for data access, and indicate optimum approaches for creating instances of objects that the application uses. The following list shows some of the most common design patterns within these groups:

• Presentation Logic
  1. Model-View-Controller (MVC)
  2. Model-View-Presenter (MVP)
  3. Use Case Controller

• Host or Behavioral
  1. Command
  2. Publish-Subscribe / Observer
  3. Plug-in / Module / Intercepting Filter

• Structural
  1. Service Agent / Proxy / Broker
  2. Provider / Adapter

• Creational
  1. Factory / Builder / Injection
  2. Singleton

• Persistence
  1. Repository