It is easy
to overlook the runat="server" attribute and assume that the control is raw HTML. This is
especially a problem late at night, when things on the monitor don??™t look as they should to
tired eyes.
The web controls provide a more consistent attribute model for specifying properties on
controls. The best example is the use of the more intuitive Text property on a Label and TextBox
control, contrasted with the Value or Name property that is used in the HtmlControls namespace.
The CSS styling support is also much better with web controls, as the web controls example
demonstrated in the CSS-related types added to the System.Web.UI.WebControls namespace.
Also, notice that web controls have an asp: tag prefix added to the HTML tag on the .aspx
page to identify the tag as a server control within a particular namespace. The classes in the
HtmlControls namespace do not have a tag prefix and cannot be used as a base class for a custom
server control.
We would have been remiss not to include a detailed discussion of what is available in the
HtmlControls namespace, as these controls can provide a potential interim step to help ease
the migration challenges to ASP.NET from ASP. However, it is our opinion that, outside the
necessary HtmlForm control for web form construction and the file upload functionality of the
HtmlInputFile control, programmers should stay away from using the HTML controls in
ASP.
Pages:
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93