Software Development

The day has arrived! Finally we have an mvc framework from the asp.net team though its currently a community preview. Have long waited for this and can’t really wait for the final release.

One of the many benefits of using a model-view-controller (MVC) architecture is that it helps to maintain a clean separation of concerns between the models, views and controllers within an application.

Now what exactly is a Model View Controller (MVC) Framework?

MVC is a framework methodology to divide an application’s implementation into three component roles: models, views, and controllers.

• “Models” are responsible for maintaining state (don’t confuse it with session state). In a more generalised terms it can be seen as a part of the application which talks to persistent data and is responsible also to provide the views with whatever data it needs.

• “Views” are the application’s user interface and are responsible for displaying the data. Typically this user interface is created off of the model data.

• “Controllers” are responsible for handling user requests, manipulating the model accordingly, and ultimately deciding which view to render to display user interface.

For a detail on MVC architecture take a look at Wikipedia’s.
Personally i think MVC eases out the process for large and complex web sites to add/remove site’s features with disturbing the whole application, but that is beyond the scope of discussion. Maybe on my next blog.

To start of i would definitely recommend developers to go through the these blogs,

Scott Guthrie’s blog on asp.net mvc

• Part 1

• Part 2

• Part 3

• Part 4

This is official microsoft page on ASP.Net MVC

Enjoy programming!

PS: Some ideas has originally been posted on Scott Guthrie’s blog.