I have seen not only in one place that the program to drag controls is rejected, but many teachers in Post Bar forums and video tutorials have said that do not drag controls for programming, microsoft's original intention for webfrom was to make web development faster and simpler. why is such a good product (or programming method) put aside? I have seen not only in one place that the program to drag controls is rejected, but many teachers in Post Bar forums and video tutorials have said that do not drag controls for programming, microsoft's original intention for webfrom was to make web development faster and simpler. why is such a good product (or programming method) put aside? Because some programmers [drag control only] is a problem =; http://ASP.NET
[Drag controls] is a good thing
Of course, the most important thing is that the two sides are ignorant, the mocking people are ignorant, and some ridiculed people are ignorant to the point where they deserve to be ridiculed... Drag controls are not a problem, but they only drag controls. The basic functions can be met, but it is difficult to control the details and cannot meet the requirements in the future. In order to make the web page feel stuck, webform does not encapsulate html like html. the whole web page is included in form, and all the submissions are post. The problem is not the control, but the drag control only uses the wheel. Drag control is not useless at any time, but at a specific time, it has more disadvantages than advantages.
Drag control is actually a simple alternative to the black box. it is a programmer who could only write command lines, and now needs a converged GUI. This scenario has four features:
- The UI logic is simple.
- UI logic and program logic are separated.
- The program has less requirements on the UI.
- Programmers are not familiar with UI programming.
You said, which of the following do you dare say you don't want to use these web applications? do you want to place a command line? With this condition, you can drag the control. However, for these web applications, user interaction is life, and the programmer's interface is perfunctory. Therefore, the professional programmers here are just for the majority of front-end developers. if you only drag controls, you are not a professional front-end programmer.
However, there are still many programmers who write professional software. they need a GUI only because the users do not have command lines. The people who write and use are both professional in the field. they do not have time to carefully study the majority of front-end knowledge. they are not professional, but they are only specialized in different directions. Http://asp.net
Now, the mvc framework has successfully avoided drag controls, which are simple and boring. The drag controls that do not challenge programmers make many junior programmers think that this is web development, in fact, he only saw a silly development method encapsulated by n layers. Webform maintains a viewstate to keep the page state. it inserts all the page-related things into this state, resulting in a very slow result. In fact, webform port the winform idea on the web end. from the perspective of the effect, this port is inappropriate. Of course, drag controls are not useless, and the development efficiency is high. it is still competent to be an enterprise-level management application for hundreds of users. Internet applications and drag controls cannot be implemented. First of all, many people only drag controls to save time. And many people don't think ahead, so they stay dragging controls.
Secondly, webform was originally designed to seize the market, and the generated web pages are the same as ie6, which is not standard (I am also drunk when a layer of form is nested under the body ), in addition, there are a lot of html code generated by controls, which is not conducive to cooperation with the artist. I vaguely remember that at that time, the company recruited the artist and asked for a meeting. net priority, drunk
Finally, B/s has evolved to the present, with a clearer division of labor and a more prominent hierarchy. In particular, front-end code is emphasized. form forms include all other elements and are the most silly way of writing. let alone header saving for speed. you can create a long string of viewstate implicit fields.
The emergence of mvc is not purely for mvc, but also to make the output more standard. After mvc3 came out in 11 years, I directly abandoned webform. In the past 15 years, many people older than me are considering switching from webform to mvc ~~ At the beginning of learning, we started from the video, and various black drag controls were followed blindly. After a period of development, I found that this mode is quite satisfactory for small projects. Ignorance
These bs and other people, too young too simple, do not understand the following two pattern:
