ASP.NET MVC 1.0 Test Driven Development: Problem - Design - Solution

1.3. Solution

So far, the problem is that we need a website to manage email distribution and the design is a set of requirements that must be met to address the problem. In the solution section, I want to talk about the technology, tools, and methodology that we will be using to envision our solution.

1.3.1. Model-View-Controller

The Model-View-Controller (MVC) is a common architectural/design pattern that is used to isolate the business logic from the user interface. This results in a loose coupling between the two that allows us to easily modify the visual presentation (the view) or the underlying business layer independently without affecting each other. In MVC, the model represents data, the view represents the user interface, and the controller manages the communication between the user's actions on the view and the model.

1.3.2. ASP.NET MVC

The ASP.NET MVC framework — as the name implies — is the Model-View-Controller framework for ASP.NET. It is different than the ASP.NET WebForms model that we have been accustomed to for the past several years. In the WebForms world, we have PostBacks, ViewStates, server-side event handling, server controls, and so on. In MVC, we don't get any of that. Some might think, "What? I can't live without these things!" and others might think "It's about time." Microsoft has gone to great lengths to emphasize the fact that the MVC framework does not and will not replace WebForms. It is simply an alternative to it.

You might ask yourself, "Which ...