Introduction to ASP. NET Server standard controls

ASP. NET controls are called ASP. NET Server standard controls, when the use of controls, sometimes you will almost forget the existence of the html language. when a problem occurs, except the business logic, you may first think of whether a control can solve my problem. I believe there are some. it may be a very complex effect, so that an encapsulated control can be solved at once. when we were familiar with the built-in controls, we began to discuss some tips for using controls, such as some advanced controls of the GridView. I also learned how to add a prompt box for buttons in the GridView ". "How to change the color when the mouse passes in the GridView" and so on. we began to enjoy writing controls to controls. property = .... N multiple statements.

If we had never touched HTML and JavaScript before, and directly moved to the war to learn ASP. NET Server standard controls, you would feel that ASP. NET is so simple. This is the initial feeling of learning controls.

Tool user

The tool users here refer to general web design tools.

I remember that when I first learned DreamWeaver, we could do a lot of JavaScript special effects in DreamWeaver. Beginners would like to do these things. at least in contact with ASP. NET, I learned html carefully, followed by DW, so I understood the html code at that time. When special effects were added, a lot of JavaScript code was generated and dizzy. when I want to modify the js part, I am afraid to correct it. in this ASP. the NET control can replace your previous dizzy feeling. It encapsulates all these js Code and won't let you see it. You just need to set the attribute. The problem is solved.
In addition, the rendering effect of the server control is not good. It is painful to let a web designer familiarize himself with a powerful custom control in the Visual Studio environment.

Learn again

Here, we can never forget that we are building Web pages and writing html. html tags will never change (except htc). When you use a new server control, you have to learn more about the properties and methods of this control. When you open IE, a large pile of html code will be generated, which has not changed in nature. your requirement is that this control can satisfy you now. It may be inaccurate after tomorrow. You may need to find another control and learn more.

Looking back, I think the final result is the same, but when using DreamWeaver, I directly saw some complicated js code. I don't need to use controls, which is troublesome, I always deal with some unfamiliar labels.

Start learning Custom Controls

I really like this technology. During the course of study, I will also have some cool effects. I don't know if you have such a habit. When using a control, you should first look at the effect. The second step is to check the source code, and the html generated in the source code is the effect. we must acknowledge ASP. NET many attribute settings are hard-coded, and the property settings of these controls can also be said to provide convenience for programming on the server side, it is very convenient to use, you can set properties.

We cannot deny the benefits of controls, and we need to use controls to make ASP. NET controls smooth.

Here, I also saw some comrades say, "I never use controls, just write html directly." Recruiters write, "familiar with html code, don't drag controls ."

Is the hard-developed controls useless? I really want to say that the knowledge required to build a control is comprehensive. Good developers need to be familiar with html, js, and css. After all, the control needs to be presented, isn't the control developer Directly Writing html? No, they just want to make the future work more convenient and do not write duplicate html code. Let the controls help you generate them.

However, there are few controls developed in China. To be honest, the built-in controls are enough. As a control user's mentality, the stronger the control, the better, so I always think that the control function is not strong enough. in addition, have you ever considered that you really need to use controls? For example, if you have used the Label control, you need to understand the html code generated by it. We are working on B/S programs, not C/S programs.

The rendering of each control has an impact on the server's performance. If you don't need it, you don't need it. We need to follow this principle. of course, this means you have to manually write the code yourself. people are inert. when you are tired of writing, you will find a way to get lazy.

Transfer control as frame

The server can program controls, and the client can also write js Code for html tags, but the page tag ID is immutable. This writing method means that the Code cannot be reused, which is a pity.
So there are some client frameworks. As a user, what is the difference?

IDE has spoiled you. Visual Studio is too advanced, and js debugging is difficult. Maybe you are familiar with background programming, and you are afraid to use some JS frameworks.

Face-to-Face Control

Why do we need to compare the controls here? I have considered performance more. let's face up to the role of the control, and we can neither degrade it nor abuse it. the stronger the control, the more code generated on the page, which has an impact on the webpage layout. It is very difficult to modify it.

Not only does ASP. NET have controls, but java Development also has struts and webwork. Isn't it just to save development time? You don't have to use controls. You think it is encapsulated when the level reaches home.
The html tag can be understood as a green version, and the control is a powerful version... the software is also divided into the full version and the green free installation version. The above introduces the standard control of the ASP. NET Server.

1. Microsoft released multiple function updates for ASP. net mvc 2 preview Edition
2. ASP. NET Server custom control security guidelines
3. Analysis of ASP. NET programming standards and Their encoding specifications
4. Introduction to ASP. NET sessions
5. ASP. NET programming tool ASP. NET Web Matrix