C.Architecture

  1. Framework Core Concepts

      1. Controller : it the first Component where your page request land , it control both how to construct data (model) and which view to load.

      2. Model : Model represent data of you business logic, it may have some business logic associates to data like validation policy.

      3. View : View are define how to render data like in terms of chart or graph , it uses model (data) provided by Controller.

      1. ASP.NET MVC framework does not use the ASP.NET Web Forms postback model for interactions with the server.

      2. Instead, all end-user interactions are routed to a controller class.

      3. As a result, ASP.NET view state and ASP.NET Web Forms page life-cycle events are not integrated with MVC-based views.

    1. REST Based URI Schema : MVC application are drive by REST based uri schema in which each action (corresponding view ) has unique URI. This model makes application very much search engine friendly

    2. IOC Container Integration

        1. MVC framework has built-in support for automatic dependency resolution based on container deceleration in configuration settings

        2. This feature allow to dynamically supply various object like database connection and web service endpoints

    3. HTML Helpers

    1. Page Inspectors

      1. Page Inspector in Visual Studio 2012 is a web development tool with an integrated browser. Select any element in the integrated browser, and Page Inspector instantly highlights the element's source and CSS.

      2. You can browse any MVC view, quickly find the sources of rendered markup, and use browser tools right within the Visual Studio environment.

      3. http://www.asp.net/mvc/tutorials/mvc-4/using-page-inspector-in-aspnet-mvc

    1. Open Source Libraries

  1. Related Patterns

    1. MVC Vs Smart UI

    2. MVC Vs MVP

    3. MVC Vs MVVM

    4. view models and domain models,

  1. References

      1. None