A brief overview on the MVC framework in Asp.net

1. What is Asp.net MVC? Prepared By : M.M.Al-FarooqueShubho http://www.linkedin.com/in/thisisshubho

2. What is MVC? A “Framework” built on top of Asp.net core framework. A framework that implements the core “Model, View and Controller” pattern where: Model = Things that encapsulates application’s Data and related Logics View = Things that handles application’s data presentation. .Controller = Things that manages application’s Flow and Navigational logics.

3. Asp.net Programming Models Two Asp.net Programming Models are there Asp.net Web Form And Asp.net MVC Both are built on top of core Asp.net Framework

4. Features of Asp.net Web Form Familiar controls and Event based Programming Model. Controls encapsulates HTML, CSS and js Rich UI controls supported that supports rich Data binding features and handling of different browsers.

5. Features of Asp.net MVC Comfortable for Traditional web development nature. Total control on HTML markup. Supports Unit testing and TDD. Extremely flexible and Extensible.

6. What programming model to choose? Both WebForm and MVC uses the same core Asp.net Libraries and Frameworks. These are: --Authentication & Authorization --Membership --Output cache, SessionState --Configuration, Deployment --Ajax and many more… So, lots of skills gained in Asp.net WebForm could be utilized in MVC

7. Why MVC? Use MVC if you like to have: Less configuration sand more conventions. More control (Driving a Motor cycle vs Driving a Car). Unit tests for the components/modules in the application (because, unlike Web Forms, MVC does not require HttpContext to load and Test.) More “Logical”, ”Understandable” and SEO friendly application URLs.

8. How MVC works?

9. How MVC works? Continued.. 1) Request arrives at the MVC Application. 2) Based upon the Routing table configuration, the URL request is mapped to an Action inside an appropriate Controller. 3) Controller accesses the Model to process the data with applying business logics. 4) Model access/retrieves database/data source and process data and return result to the Action. 5) Action populates the view with processed data and the View renders UI.