Asp. NET extract--server-side control article (preface)

We know that ASP. NET Web Forms add support for server-side controls, characterized by the addition of the runat= "server" attribute to the HTML markup of the control. The control that owns this tag, whose instance is generated on the server side, is responsible for converting the. NET Framework to normal HTML markup and outputting it to the client. The process of this transformation is an extremely important basis for asp.net. Why, then?

Friends who are familiar with HTML development should have a good understanding of the controls needed to write Dynamic Web pages (FORM, INPUT ...). ）。 And ASP.net provides us with richer user interface interaction elements-server-side controls (simple button, Label, complex data controls including DataGrid)--they are the most intuitive part of ASP.net's powerful features.

You may have a question: How does a server-side control run on a client? The HTML specification does not have their shadow, but the client does not need a special environment to navigate the ASP.net page normally. How is this done?

Conversion--as if communication between the two heads of state needs to be translated, to allow server-side controls to be properly identified and run by the client, requires a conversion process-that is why the. NET framework exists.

The. NET framework transformation for controls is very complex, but as long as we understand the rules, we can use them.