Introduction to ASP.NET MVC
Download as PPT, PDF•2 likes•4,075 views
The document introduces ASP.NET MVC, which is a framework from Microsoft that builds on the standard ASP.NET engine. It follows the model-view-controller (MVC) pattern to separate application behavior, user interface, and data access. The goals of ASP.NET MVC include testability, friendly URLs, leveraging existing ASP.NET features, and full control of HTML. It also discusses how ASP.NET MVC works, including routing, controllers, actions, and views. Demos are provided for basic routing and controllers as well as models, HTML helpers, forms, and validation.
![Request variable Action method parameter ModelBinder Handling post request Public ActionResult Create() { string subject = Request.Form[“Subject”]; } Public ActionResult Create( string Subject ) { // do something } Public ActionResult Create( Commentary commentary ) { // do something }](https://image.slidesharecdn.com/aspnetmvc-091216083112-phpapp02/85/Introduction-to-ASP-NET-MVC-15-320.jpg)
Introduction to ASP.NET MVC
- 1. Introduction to ASP.NET MVC
- 2. Agenda What's MVC What's ASP.NET MVC Goals of ASP.NET MVC How does it work?
- 3. What's MVC View Model Controller Defines application behavior Maps user action to model Select view to response Represent enterprise data Business rules that govern access/update data Render content of model
- 4. What's ASP.NET MVC New framework from Microsoft that builds on top standard ASP.NET engine ASP.NET Web Form ASP.NET MVC Core standard ASP . NET engine Microsoft .NET Framework
- 5. Goals of ASP.NET MVC Testability Pluggable Friendly URLs (REST URL) Existing ASP.NET feature still available Full control of HTML Open source
- 6. ASP.NET MVC ASP.NET MVC 1.0 (Dec, 2008) ASP.NET MVC 2.0 Beta (Nov, 2009)
- 7. ASP.NET MVC .NET Framework 3.5 Visual Studio 2008 (service pack 1) Download ( asp.net/mvc ) Visual Studio 2010 (included)
- 9. Controller is responsible for handling incoming request Routing system decides how URLs map into particular controllers and actions How does it work? Action in controller Controller http://localhost:1725/ Hello / ActionTest
- 10. Component is first hit by a request The rules are configured in Global.asax Routing public static void RegisterRoutes(RouteCollection routes) { routes.MapRoute( "Default", "{ controller }/{ action }/{ id }", new { controller = "Home", action = "Index", id = "" } ); } http://localhost:1725/ Product / Show / 1
- 11. Demo: Model with Strong type
- 12. Request Flow Request View Controller Model HTTP Select View HTML Routing Select Controller
- 13. Demo: HTMLHelper
- 14. Provide method for creating HTML control Support Strong-type HTML Helper <%= Html. TextBoxFor (model => model. Body ) %> <input type=“text” name=“ Body ” id=“ Body ” />
- 15. Request variable Action method parameter ModelBinder Handling post request Public ActionResult Create() { string subject = Request.Form[“Subject”]; } Public ActionResult Create( string Subject ) { // do something } Public ActionResult Create( Commentary commentary ) { // do something }
- 16. Demo: Form & Validation
- 17. Validation Define Validation in Model Server Side Validation Client Side Validation ModelState Class to keep state of model Data Annotation Model Binder Java script
- 18. Summary RESTful URL Complex URL F ull control over HTML Clean HTML Event - driven programming (Drag n’ drop) Design for testing Cannot test easily Separation of Concerns Combines code and view ASP.NET MVC ASP.NET WebForms
- 19. Q & A
Editor's Notes
- #4: Main purpose of mvc is to isolate business logic from user interface pros - Better maintain - Testable - Cleaner code
- #6: Testability - Framework provides interface-base easy to mackable Pluggable - Every component can easy replaced or customize (view replaced with ironPython) - Easy to use dependency injection design pattern (unity, spring) Friendly URL - Can build app for search engine friendly Existing ASP,NET feature still available - All exist asp.net feature still available ex: Master.Page, User Control, Session, Memberdhip - But ViewState and page life cycle are not support Full control of HTML - Write only html - no viewstate Open source - under MS-PL license
- #9: Demo from empty project Show create view and run Show ViewData and run Demo TDD hello world
- #10: Controller is responsible for handling incoming request - All public method that implement by Controller class, It can be invoke from web via url.
- #11: Controller is responsible for handling incoming request - All public method that implement by Controller class, It can be invoke from web via url.
- #12: Demo new template project Modify routing default to commentary Create model Commentary Create Commentary controller Create View Show F5 Create Method Details Use Model.Subject
- #14: Demo new template project Modify routing default to commentary Create model Commentary Create Commentary controller Create View Show F5 Show feature for HTML helper Show JSON JsonRequestBehavior.AllowGet
- #17: Show validation with statemodel Show validation with anotation in serverside Show validation with client
- #18: Using ModelState Class => Encapsulates the state of model binding to a property of an action - method argument, or to the argument itself
- #19: Uses the ‘Page Controller’ pattern . Each page has a code - behind class that acts as a controller and is responsible for rendering the layout . 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