In addition to
(or instead of) using <% %> code blocks to program dynamic content,
ASP.NET page developers can use ASP.NET server controls to program Web pages.
Server controls are declared within an .aspx file using custom tags or
intrinsic HTML tags that contain a runat="server" attributes
value. Intrinsic HTML tags are handled by one of the controls in the System.Web.UI.HtmlControls
namespace. Any tag that doesn't explicitly map to one of the controls is
assigned the type of System.Web.UI.HtmlControls.HtmlGenericControl.
Server controls
automatically maintain any client-entered values between round trips to the
server. This control state is not stored on the server (it is instead stored
within an <input type="hidden"> form field that is
round-tripped between requests). Note also that no client-side script is
required.
In addition to
supporting standard HTML input controls, ASP.NET enables developers to utilize
richer custom controls on their pages. For example, the following sample
demonstrates how the <asp:adrotator> control can be used to
dynamically display rotating ads on a page.
2.
ASP.NET
Web Forms pages can target any browser client (there are no script library or
cookie requirements).
3.
ASP.NET
Web Forms pages provide syntax compatibility with existing ASP pages.
4.
ASP.NET
server controls provide an easy way to encapsulate common functionality.
5.
ASP.NET
ships with 45 built-in server controls. Developers can also use controls built
by third parties.
6.
ASP.NET
server controls can automatically project both uplevel and downlevel HTML.
7.
ASP.NET
templates provide an easy way to customize the look and feel of list server
controls.
8.
ASP.NET
validation controls provide an easy way to do declarative client or server data
validation.
No comments:
Post a Comment