Which pattern to use with a typical Web Form?

Question

I am writing a simple ASP.NET Web Forms application. I want to improve the code by implementing any design pattern with which abstraction is achieved and increases manageability and understandability.

Which pattern is recommended? Please also provide links to sample applications.

Answer 1

You might consider using the Model-View-View model MVVM pattern. It is a derivative of MVC, but is designed / intended to be used in exactly the situation you describe. There is a wealth of information on the MSDN site if you don't feel like googling it.

MVVM facilitates a clear separation of the development of the graphical user interface 
(either as markup language or GUI code) from the development of the business logic or back 
end logic known as the model (also known as the data model to distinguish it from the view 
model). The view model of MVVM is a value converter[4] meaning that the view model is 
responsible for exposing the data objects from the model in such a way that those objects 
are easily managed and consumed. In this respect, the view model is more model than view, 
and handles most if not all of the view’s display logic (though the demarcation between 
what functions are handled by which layer is a subject of ongoing discussion[5] and 
exploration). The view model may also implement a mediator pattern organising access to the 
backend logic around the set of use cases supported by the view.

Answer 2

With ASP.NET Web Form, you typically use the Model View Presenter pattern.

GlenH7 mentioned on his answer about MVVM, while it is an elegant pattern, ASPX Webform just doesn't have great support for that. MVVM is more popular in the WPF world.

Answer 3

The one thing you need to avoid at all costs is the WebForms anti-pattern of putting logic in your code-behind. Whether you use MVP or a flavor of that or not, your code-behind files should be very sparse for the sake of your sanity.

Answer 4

Short answer is : look at MVP pattern that avoids potential code-behind asp.net forms issue by loosely coupling (de-coupling) your view and logic.

You may also want to go one step further and look at comparison MVC, MVP, ASP.NET.

The following posts are good entry points and examples:

• Model View Presenter with ASP.NET
• Better Web Forms with the MVP Pattern
• MVC vs. MVP vs. MVVM