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

What is the understanding of the .NET MVC Framework? for this problem, this article introduces the corresponding analysis and solutions in detail, hoping to help more partners who want to solve this problem to find a simpler and easier way.

Recently, I have found that there are a lot of articles about the .NET MVC Framework, and all of them are very good and profound. I have probably read them today.

By the way, I made a small guestbook with it, and here I would like to share my experience!

I would like to say that what touches me most is its handling of httphandler. People who have studied ASP.NET may know that there is actually only one httphandler per page. I remember that when I first came into contact with address mapping technology at that time, it took a lot of work to configure paths and mapping rules in the configuration file, and to implement Ihttphandler or ihttpmodule interfaces, which may not be an easy task for novice ASP.NET users. But now that the mvc framework takes care of most of the tasks for us, all we have to do is write our rules, which may be an incidental feature!

Second: there is no need to write a separate class file for a single page. I remember that when I first wrote the ASP.NET program, because the code-behind page of the ASP.NET page is actually a separate class assigned to each page, it allocates the namespace in the form of a folder, so there will be a problem that a lot of irregular naming dll will be generated when the website is released. Finally, I found out the rule of a class for each page, and finally solved the problem of irregular naming of dll. I think it took a lot of effort. But now the mvc framework has also solved this problem for us, and the solution can be said to be more thorough, it corresponds each page to a method in a class, as long as the class name corresponds to the method name, and the data submission method such as post or get has also been greatly improved!

Third: when I first built the MVC project, I found that it is better suited to the multi-tier development model of ASP.NET. If you do not adopt a three-tier architecture or more layers of development architecture, it may be a very incredible thing if you use the development framework of mvc.

Fourth: it better combines the ASP.NET Ajax framework, which makes it more convenient and flexible for you to develop with MVC+Ajax!

Fifth: in the ASP.NET MVC framework, you can also automatically generate Model and other functions by dragging and dropping tables.

For its advantages may be said alone is endless, can only through specific projects to continue to learn and conduct in-depth research, because I am not yet installed on the computer. Net 3.5, so tonight can not do a specific project demonstration for you, this article can also be used as the next ASP.NET MVC project development demonstration of a preface, due to the work, three-tier architecture examples have been no time.

The answer to the question about the understanding of the .NET MVC Framework is shared here. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.

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.