ASP.Net MVC - An Introduction

What is MVC?

             Several Months ago, I just started to learn new technologies in order to teach other thru a weekly technical session in my current company. So I decide to lean ASP.Net MVC. These points are from my learning.

So what is ASP.Net MVC?

             According to Microsoft, ASP.Net MVC is a new paradigm to design a website using Model, View and Contoller Pattern. The first 3 letters of Model, View and Controller forms the name MVC. However MVC newly introduced in ASP.Net but MVC is not a new framework it has been already used in Java and PHP etc.

What is the Need?

             Yeah really it’s a good question. I have also had the same in my mind when I start learning. Because Microsoft already had a very well defined and more successful Web Forms on their hand. So why they introduced the MVC in ASP.Net?

Problems in ASP.Net Web Forms:

               Every ASP.Net developer must have a good experience with Web forms. Since it’s easy to design with Visual studio (believe guys we have developed used drag and drop development like in classic Windows Form Development in web form with lot of predefined events), Have a predefined page life cycle, easy to learn etc. 

              When Microsoft followed its drag and drop methodology in Web development entire world are astonished and give red carpet. However, after year by year, the needs change everything. That is the developers know the pain of Web forms. Some pains are:

1.     Web forms by nature hide all the nature of HTTP.
2.        The user has no more control on the HTML markup generated by Web forms.
3.     There is no separation of Concerns in web forms. Presentation and business logics are tightly coupled in web form. For example, ASPX and ASPX.VB (or) ASPX.CS files are tightly coupled or depend one another. You cannot differ or separate the Design (Presentation Logic) and Code Logic.  So there is no place of SOC.

 The above are the main reasons for the introduction of ASP.Net MVC. 

Hope this helps!!