Custom controls from ASP.NET Quick Start Tutorial
Directory 1. Generation logic 2 of the control 2. Develop a composite control 3. Processing events 4 in the composite control. Custom event 5 is triggered from the composite control. Maintenance status 6. Develop a custom (non-composite) control 7 for retrace data. Send a client javascrip 'for custom back ------------------------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------- -
1. Control generated logic Each control has a controls property inherited from system.web.ui.control. This is a collection attribute indicating the child control (if any) of the control. If the control does not use the PARSECHILDRENATTRIBUTE tag or tagged as Parsechildrenattribute (ChildrenasProperties = false) When the control is used on the page, the ASP.NET page framework will apply the following analysis logic. If the analyzer encounters a nested control in the tag of the control, it will create an instance of a nested control and add them to the control of the controls attribute. The text between the tag is added to LiteralControl. Any other nested elements generate an analyzer error.
EXP '*********************************************************** ************************************************************ SIMPLEINNERCONTENT.ASPX
<% @ Register tagprefix = "simpleControlsamples" Namespace = "SimpleControlsamples"
AskEMBLY = "SimpleControlsamplesVB"%>