Session 1
Download as PPTX, PDF0 likes527 views
The document provides an overview of the ASP.NET MVC framework. It describes the core components of MVC - Models, Views, and Controllers. Models represent the application's data, Views display the UI, and Controllers handle user input and interaction. It also discusses when to use MVC vs Web Forms, the advantages of each, and new features in MVC 3. The standard project structure for MVC is also outlined.
Ad
More Related Content
What's hot (20)
Viewers also liked (20)
![Service Inzicht [Compatibiliteitsmodus]](https://cdn.slidesharecdn.com/ss_thumbnails/serviceinzichtcompatibiliteitsmodus-13025493892095-phpapp01-thumbnail.jpg?width=560&fit=bounds)
Ad
Similar to Session 1 (20)
Ad
Recently uploaded (20)
Session 1
- 2. Models. Model objects are the parts of the application that implement the logic for the application's data domain. For example, a Product object might retrieve information from a database, operate on it, and then write updated information back to a Products table in a SQL Server database.Views. Views are the components that display the application's user interface (UI). Typically, this UI is created from the model data. An example would be an edit view of a Products table that displays text boxes, drop-down lists, and check boxes based on the current state of a Product object.Controllers. Controllers are the components that handle user interaction, work with the model, and ultimately select a view to render that displays UI. In an MVC application, the view only displays information; the controller handles and responds to user input and interaction. For example, the controller handles query-string values, and passes these values to the model, which in turn might use these values to query the database.
- 3. When to Create an MVC ApplicationYou must consider carefully whether to implement a Web application by using either the ASP.NET MVC framework or the ASP.NET Web Forms model. The MVC framework does not replace the Web Forms model; you can use either framework for Web applications. (If you have existing Web Forms-based applications, these continue to work exactly as they always have.)Before you decide to use the MVC framework or the Web Forms model for a specific Web site, weigh the advantages of each approach.
- 4. Advantages of an MVC-Based Web ApplicationThe ASP.NET MVC framework offers the following advantages:It makes it easier to manage complexity by dividing an application into the model, the view, and the controller.
- 5. It does not use view state or server-based forms. This makes the MVC framework ideal for developers who want full control over the behavior of an application.
- 6. It uses a Front Controller pattern that processes Web application requests through a single controller. This enables you to design an application that supports a rich routing infrastructure.
- 7. It provides better support for test-driven development (TDD).
- 8. It works well for Web applications that are supported by large teams of developers and for Web designers who need a high degree of control over the application behavior.Advantages of a Web Forms-Based Web ApplicationThe Web Forms-based framework offers the following advantages:It supports an event model that preserves state over HTTP, which benefits line-of-business Web application development. The Web Forms-based application provides dozens of events that are supported in hundreds of server controls.
- 9. It uses a Page Controller pattern that adds functionality to individual pages.
- 10. It uses view state on server-based forms, which can make managing state information easier.
- 11. It works well for small teams of Web developers and designers who want to take advantage of the large number of components available for rapid application development.
- 12. In general, it is less complex for application development, because the components (the Page class, controls, and so on) are tightly integrated and usually require less code than the MVC model.The ASP.NET MVC framework provides the following features:Separation of application tasks (input logic, business logic, and UI logic), testability, and test-driven development (TDD)
- 13. An extensible and pluggable framework. The components of the ASP.NET MVC framework are designed so that they can be easily replaced or customized. You can plug in your own view engine, URL routing policy, action-method parameter serialization, and other components. The ASP.NET MVC framework also supports the use of Dependency Injection (DI) and Inversion of Control (IOC) container models. DI enables you to inject objects into a class, instead of relying on the class to create the object itself. IOC specifies that if an object requires another object, the first objects should get the second object from an outside source such as a configuration file. This makes testing easier.Extensive support for ASP.NET routing, which is a powerful URL-mapping component that lets you build applications that have comprehensible and searchable URLs
- 14. Support for using the markup in existing ASP.NET page (.aspx files), user control (.ascx files), and master page (.master files) markup files as view templates. You can use existing ASP.NET features with the ASP.NET MVC framework, such as nested master pages, in-line expressions (<%=ย %>), declarative server controls, templates, data-binding, localization, and so on.
- 15. Support for existing ASP.NET features. ASP.NET MVC lets you use features such as forms authentication and Windows authentication, URL authorization, membership and roles, output and data caching, session and profile state management, health monitoring, the configuration system, and the provider architecture.MVC 3 New Features MVC Vs WebForms
- 16. MVC Project Structure App_Data, which is the physical store for data. This folder has the same role as it does in ASP.NET Web sites that use Web Forms pages.
- 17. Content, which is the recommended location to add content files such as cascading style sheet files, images, and so on. In general, the Content folder is for static files.
- 18. Controllers, which is the recommended location for controllers. The MVC framework requires the names of all controllers to end with "Controller", such as HomeController, LoginController, or ProductController.Models, which is provided for classes that represent the application model for your MVC Web application. This folder usually includes code that defines objects and that defines the logic for interaction with the data store. Typically, the actual model objects will be in separate class libraries. However, when you create a new application, you might put classes here and then move them into separate class libraries at a later point in the development cycle.
- 19. Scripts, which is the recommended location for script files that support the application. By default, this folder contains ASP.NET AJAX foundation files and the jQuery library.
- 20. Views, which is the recommended location for views. Views use ViewPage (.aspx), ViewUserControl (.ascx), and ViewMasterPage (.master) files, in addition to any other files that are related to rendering views. The Views folder contains a folder for each controller; the folder is named with the controller-name prefix. For example, if you have a controller named HomeController, the Views folder contains a folder named Home. By default, when the ASP.NET MVC framework loads a view, it looks for a ViewPage (.aspx) file that has the requested view name in the Views\controllerName folder. By default, there is also a folder named Shared in the Views folder, which does not correspond to any controller. The Shared folder is used for views that are shared across multiple controllers. For example, you can put the Web application's master page in the Shared folder.
- 21. In addition to the folders listed previously, an MVC Web application uses code in the Global.asax file to set global URL routing defaults, and it uses the Web.config file to configure the application.