(HtmlTable). There is no server-side aspect to any HtmlControl, unless you add a runat=”server” attribute to it. Adding this attribute gives you server-side control over the client-side HTML. You can create an HtmlControl from any client-side
HTML element. There are several ready-made HtmlControls, and an HtmlGenericControl which you can use for any other HTML element.
This is the base Class for any ASP.Net Control that uses an HTML Template. There are 2 ready-made classes in the CLR that inherit this class.
System.Web.UI.Page, and System.Web.UI.UserControl. Generally, when people talk about “Web Controls,” they are talking about HtmlControls, WebControls, or the UserControl class, and not the Page class, although the Page class is, in fact a “Web Control” (Note the space in the term, which distinguishes “Web Control” from the class WebControl).
A UserControl is a Templated Control that is a container for pure HTML and other Web Controls. Of all the “Web Controls” that are used frequently in ASP.Net, the UserControl is the only one that has an HTML Template. It allows a block of HTML and server-side Controls to be treated as a single unit, or Control.
This is a NameSpace, not a class. It has 6 different top-level classes:
This class is used to encapsulate pure HTML in a container. It does nothing else. As ASP.Net is fully object-oriented, any HTML in a template that is not a server-side control is encapsulated in a Literal Control at run-time. It can also be used to pop any block of HTML into a Page or Control at run-time.
This class is used, quite literally, as a “place holder.” It renders no HTML, but as a “Web Control,” (System.Web.UI.Conrol) it has a Controls Collection to which any other Control can be added. As it exists in a certain location in a Page or other Control, any Control can be popped into it at run-time. A UserControl could be used for this, by not having anything in it. But what would the purpose of the Template be? This class is not Templated, so it is easier to work with for this purpose.
These 2 WebControls comprise a Repeater Control. The Repeater is a container for RepeaterItems. In addition, it has properties that allow for the addition of a number of System.Web.UI.ITemplate classes for fomatting the data contained in it. A Repeater is a sort of hybrid. While it is not a Templated Control, it is hosted in a Templated Control, and the Templates in it are placed in the Template of the hosting Templated Control. It is used for binding aggregate data (arrays, Collections, etc) to a block of repeating HTML in any format desired.
This is the base class for most of the Controls that are often confused with HtmlControls. A WebControl is a Control that ALWAYS has a server-side component, and WebControls all share the same fields, properties and methods of System.Web.UI.WebControl. In addition, each WebControl has fields, properties, and methods that correspond uniquely to the type of HTML element that the WebControl renders and interacts with at run-time.
HtmlControls are, therefore, by nature, leaner (consume less resources) than WebControls, but have less functionality as well.
This class displays XML without any formatting or using XSLT. It is genreally used to display embedded XML in a web page.
In summary, the term “Web Control” is a fairly common, and confusing term that is generally used to encompass HtmlControls, WebControls, and the UserControl ASP.Net System.Web.UI.Control classes. It is important to distinguish between what type of “Web Control” is being discussed. The main differences between these 3 types of Controls are:
HtmlControls are lightweight Controls that can represent pure HTML, or add server-side functionality to client-side HTML.
WebControls are Controls that always have a server-side class associated with them, and provide a common server-side functionality for working with various HTML elements, and specific functionality for specific HTML elements.
A UserControl is a Templated Control which has a Template file, a container for both pure HTML and server-side class references in it, and allows for server-side manipulation of the server-side Controls in it. It allows a block of HTML and server-side Controls to be treated as a single unit, or Control.[/quote]