All server controls must appear within a
The ASP.NET Web Forms page framework is a scalable common language runtime programming model that can be used on the server to dynamically generate Web pages.
Have you ever found yourself using one of the built-in ASP.NET server controls and needed to add some trivial extra functionality? For example, maybe for a Button Web control you wanted a confirm client-side dialog box to appear, requiring the user to click OK to actually submit the form, or maybe you wanted to enhance the DataGrids output so that whenever the user moused over a cell, the cells background color changed to a "highlighted" color. …..
Like HTML server controls, Web server controls are also created on the server and they require a runat="server" attribute to work. However, Web server controls do not necessarily map to any existing HTML elements and they may represent more complex elements.
ASP.NET has solved the "spaghetti-code" problem described above with server controls.
Server controls are tags that are understood by the server
The TextBox control is used to create a text box where the user can input text.
The TextBox control generates single-line and multiline text boxes.
This section of the QuickStart demonstrates how advanced developers can write their own ASP.NET server controls that work within the ASP.NET page framework. By writing your own custom ASP.NET server controls, you can encapsulate custom user interface and other functionality in controls that can be reused on ASP.NET pages. The QuickStart provides an introduction to authoring custom controls through hands-on examples. For more information about control authoring, see Developing ASP.NET Server Controls in the Microsoft .NET Framework SDK documentation.
his section of the QuickStart demonstrates how advanced developers can write their own ASP.NET server controls that work within the ASP.NET page framework. By writing your own custom ASP.NET server controls, you can encapsulate custom user interface and other functionality in controls that can be reused on ASP.NET pages. The QuickStart provides an
Introduction: After working with ASP.Net for over a year, and participating in the Microsoft ASP.Net newsgroups for quite awhile, I have observed that many people who are new to ASP.Net are having some fundamental difficulties understanding how it actually works. This is particularly important with ASP.Net, much more so than with ASP. Why? Because ASP has a fairly straightforward approach to creating dynamic content, and is procedural. ASP.Net is object-oriented, and has a number of features built in which seem to confuse people. For example, with ASP it was fairly obvious to most of us that there is an impenetrable gulf between the server and client, because HTTP is stateless, meaning that the browser and server only respond to individual page requests, and do not maintain any kind of state between requests.............................
