Shulou(Shulou.com)06/02 Report--

This article mainly introduces "what are the advantages of ASP.NET MVC1.0". In daily operation, I believe many people have doubts about the advantages of ASP.NET MVC1.0. The editor consulted all kinds of materials and sorted out simple and easy-to-use methods of operation. I hope it will be helpful for you to answer the doubts about "what are the advantages of ASP.NET MVC1.0?" Next, please follow the editor to study!

1. The composition of MVC

Models: access the database, load data, and process business logic. It is embodied in the project as the data entity class plus the business proxy class.

Views: display data, user interface. It is represented as an aspx page in the project, with code-behind occasionally added.

Controller: according to the routing rules, the requested data is transmitted to the specified page for display, or the data entered by the user can be passed to the logical processing class. It can contain simple validation logic. Data access logic should not be included.

2. Why use MVC

The purpose of MVC is to improve development efficiency and testability. According to the official ASP.NET MVC 1.0 guide (hereinafter referred to as the guide), MVC-based Web applications have the following advantages:

[1] it is more convenient to manage complex programs.

It makes it easier to manage complexity by dividing an application into the model, the view, and the ontroller.

[2] higher controllability in development

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.

[3] Routing makes software design more flexible

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.

[4] more suitable for test-driven development

It provides better support for test-driven development (TDD).

[5] higher controllability in team development projects

It works well for Web applications that are supported by large teams of developers and Web designers who need a high degree of control over the application behavior.

At the same time, the MVC framework has the following characteristics:

[1] dividing the application into components is more convenient for testing. The MVC framework is interface-based, so you can use MOCK to replace your actual classes; when doing unit tests, you don't have to run Contrllers, which makes the tests faster and more flexible.

[2] the MVC framework is extensible, and you can design and replace video engines, URL guidance rules, Action parameter sequences, and so on. At the same time, the MVC framework also supports dependency injection and control inversion, you can inject instances from the outside, instead of letting the class create its own instances, you can also create instances through configuration files, which makes testing easier.

[3] the powerful URL mapping component makes your application's URL easier to understand and has the ability to search. Your URL does not have to include file paths, and this design is suitable for custom query engines and REST schemas.

[4] the MVC framework still supports pages, user controls, and master pages in ASP.NET as templates for views; at the same time, you can also use nested master pages, inline expressions (in-line expressions), server-side controls, templates, data binding, localization, and other things that ASP.NET already has.

[5] at the same time, FORM authentication, Windows authentication, URL authorization, Membership, role, output, data cache, Session, Profile state management, configuration, Provider framework and other features in ASP.NET are still available in the MVC framework.

Summary: the ASP.NET MVC 1.0 framework is based on ASP.NET, so it includes almost all the features in ASP.NET. At the same time, he provides designers with a set of testing solutions (of course, this is common to all language platforms MVC patterns). A lot of features have been added to the VS2008 where the framework is installed, and you can easily add Views, Models, and Controllers.

3. Compare with the three-tier ASP.NET application

Compared with ordinary ASP.NET, the difference of * * lies in the foreground development, and the database access and logical processing included in the background are not significantly different from the previous methods. In the MVC framework, these are collectively referred to as Model. In the three-tier structure, these can be called data access layer and logical processing layer.

[1] Page development

Sites developed in this mode do have less code to look at the page than before, but it uses more page scripts () to display data. The guide does not mention that server-side controls are not recommended, but it provides a large number of HTML HELPER and allows you to add Helper yourself, such as DataGridHelper, so it is more convenient to use these Helper in the MVC framework, but this should not have much impact on skilled workers, because in actual development we use Ctrl+C/Ctrl+V more often, and it takes about the same time to copy a few tags and copy a few Helper methods. It may be faster for beginners to use these Helper if they are not familiar with tags, but this will affect novice mastery of tags, which is really contradictory.

[2] data submission

Ordinary ASP.Net developers may also need to set up data binding or write encapsulation code in code-behind when submitting data; in MVC, the framework automatically helps you to encapsulate the data filled in the page into a pre-specified Model, and the data submission operation is very convenient in the MVC framework. And in normal ASP.NET pages, there is often a situation where an attribute cannot be tied back, which should be resolved in MVC. It is mentioned in the guide that the use of Routing makes it more convenient for applications under the MVC framework to operate custom queries. In fact, there is not much difference between the query and the ordinary way, which parses the encapsulated classes. As for "URL is easier to understand", now applications click from the interface to implement operations, few people will pay attention to URL itself, so this advantage is not an advantage.

[3] Unit test

In terms of testing, the MVC framework does a good job, and it is more convenient to test with MOCK. A good WEB application design should separate the page presentation from the logic. Ordinary ASP.NET applications can also do this. The key lies in the design.

At this point, the study on "what are the advantages of ASP.NET MVC1.0" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.