MVC Architecture in ASP.Net By Nyros Developer
Download as PPT, PDF•2 likes•4,303 views
This document provides an overview of ASP.NET MVC, comparing it to Web Forms. It states that MVC is not a replacement for Web Forms but an additional option, using a separation of concerns approach. The MVC flow involves URLs routing to controllers and actions. Key advantages of MVC include testability, clean separation of concerns, and support for Ajax, security, and routing. When choosing between MVC and Web Forms, factors include architectural patterns, testability, and expertise with HTML, CSS, and JavaScript required.
MVC Architecture in ASP.Net By Nyros Developer
- 2. Agenda What is ASP.NET MVC What is MVC MVC Flow Routing Using Ajax & Security Choosing Between MVC and Web forms Which one is better ? Summary
- 3. What is ASP.NET MVC? A new Web Application Project type Simply an option Not a replacement for WebForms Builds on top ASP.NET Manual vs Automatic Transmission
- 4. What is MVC? Model Controller View
- 5. Separation Of Concerns Each component has one responsibility SRP : Single Responsibility Principle More easily testable Helps with concurrent development
- 6. Not the new Web Forms 4.0 Not replacing Web Forms, but Adds to it It can not use Web Controls Not a whole new engine but sits on ASP.NET engine Not the best solution for REST What MVC is not ?
- 7. Maintain Clean Separation of Concerns Extensible and Pluggable Enable clean URLs and HTML Great integration within ASP.NET Tooling Support
- 8. MVC Flow
- 11. URLs -> application -> Controller Action Construct outgoing URLs Constructed URLs can be used to call back to Controllers/Actions Routing Engine
- 12. Sequence Diagram ASP.Net MVC Flow
- 13. Ajax is not just “Update Panel” You can use Page methods Web Services They all require you to write a lot of javascript MVC Ajax helps with Forms and ActionLinks !! Ajax Support
- 14. Built in Controller for Logging Using ASP.NET Security Providers Having the ability to control the security level of each controller method Security Support
- 15. Choosing Between WebForms and MVC Now that Asp.Net is much more mainstream at work, The question is asked time and again as to which one should be used while developing a Web Application. One possible way to answer this question is to do a analysis of both the frameworks.
- 18. ASP.Net MVC VS Web Forms Uses the ‘Front Controller’ pattern. There is a single central controller for all pages to process web application requests and facilitates a rich routing architecture At its core, ASP.NET MVC was designed to make test-driven development easier. You ‘can’ test your Controller without instantiating a View and carry out unit-tests without having to run the controllers in an ASP.NET process. Uses the ‘Page Controller’ pattern. Each page has a code-behind class that acts as a controller and is responsible for rendering the layout. At its core, you ‘cannot’ test your controller without instantiating a View. There are ways to get around it using tools
- 19. ASP.Net MVC VS Web Forms A thorough understanding of how HTML, CSS and JavaScript work together is required. The advantage is you can do a lot of jQuery and AJAX stuff in an efficient and simple manner than you would do in an ASP.NET application. You lose the 'drag and drop' quick model of building your web applications. Deep understanding of HTML, CSS and JavaScript is not required to a large extent since the WebForm model abstracts a lot of these details and provides automatic plumbing. While abstracting details to provide ease of use, sometimes a solution is overcomplicated, than it needs to be. Can drastically reduce time while building up intranet and internet applications that use a lot of controls (drag and drop model).
- 20. WebForms ??????? MVC ?????? Which one is better ?
- 22. Summary Not a replacement for WebForms – All about alternatives Fundamental – Same team that builds WebForms