Mvc part 1


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Mvc part 1

  1. 1. Mazda Consultance Pvt. Ltd. MVC Architecture
  2. 2. What is ASP.NET MVC ?• A new Web Application Project type• Separation of concerns• Built on top of ASP.NET platform• Tight control over HTML• Designed to be testable• Extensible routing system• Better integration with 3rd party libraries• Open source• Language innovations
  3. 3. What MVC is?• Maintain Clean Separation of Concerns• Extensible and Pluggable• Enable clean URLs and HTML• Great integration within ASP.NET• Tooling Support
  4. 4. Advantages of MVC are:• Separation of concerns (SoC) : - – From a technical standpoint, the organization of code within MVC is very clean, organized and granular, making it easier (hopefully) for a web application to scale in terms of functionality. Promotes great design from a development standpoint.• Easier integration with client side tools (rich user interface tools) :- – More than ever, web applications are increasingly becoming as rich as the applications you see on your desktops. With MVC, it gives you the ability to integrate with such toolkits (such as jQuery) with greater ease and more seamless than in Web Forms.
  5. 5. Advantages of MVC are:• Search Engine Optimization (SEO) Friendly / Stateless :- – URLs are more friendly to search engines (i.e. 1 - retrieve user with an ID of 1 vs mywebapplication/users/getuser.aspx (id passed in session)). Similarly, since MVC is stateless, this removes the headache of users who spawn multiple web browsers from the same window (session collisions). Along those same lines, MVC adheres to the stateless web protocol rather than battling against it.
  6. 6. Advantages of MVC are:• Works well with developers who need high degree of control : - – Many controls in ASP.NET web forms automatically generate much of the raw HTML you see when an page is rendered. This can cause headaches for developers. With MVC, it lends itself better towards having complete control with what is rendered and there are no surprises. Even more important, is that the HTML forms typically are much smaller than the Web forms which can equate to a performance boost - something to seriously consider.• Test Driven Development (TDD) : - – With MVC, you can more easily create tests for the web side of things. An additional layer of testing will provide yet another layer of defense against unexpected behavior.
  7. 7. MVC Model ModelView Controller
  8. 8. MVC Flow ControllerRequest Step 1 Incoming request directed to Controller
  9. 9. MVC Flow Controller ModelStep 2Controller processes request and forms a data Model
  10. 10. MVC Flow Controller ViewStep 3Model is passed to View
  11. 11. MVC Flow Controller ViewStep 4View transforms Model into appropriate output format
  12. 12. MVC Flow Controller View ResponseStep 5Response is rendered