Common Metadata and base classes of AjaxControlToolkit

Top 10 common metadata

Most of the above attributes are setRenderingTo make it easier to call the real implementation of the script, you still need the script.

The above metadata has helped us save a lot of effort, and once again played its role. A very useful thing.

Three basic categories

Both the IextenderControl and IscriptControl interfaces are provided to implement the extension. They are only in different ways. The first method must be used together with the original control. The second excuse is to directly inherit from the original control for the extension.

The ExtenderControl and ScriptControl abstract classes are also provided. this is just like adding the CompositeControl class to the InamingContainer interface of the CompositeControl Control in the composite control. However, you still need to implement the AjaxControlToolkit interface to re-expand the two classes, it provides ExtenderControlBase and ScriptControlBase. it cleverly utilizes the metadata feature to make the backend control settings more convenient. We don't need to implement IextenderControl and Other interfaces. Each of them provides the ScriptPath attribute to reference external scripts. the file also provides an IclientStateManager interface to save data after foreground operations and then return it to the background ExtenderControl. The IclientStateManager interface is not implemented, but the ClientState attribute is also provided. scriptControl also implements the ICallbackEventHandler interface to implement client callback.

In addition, the third class is the ScriptUserControl class. It inherits the content implemented by the class and similar user controls. This class can be inherited to extend the above features. Most of the functions can be used flexibly only by using scripts.

Http://www.itpub.net/thread-866780-1-1.html

Http://www.cnblogs.com/Clingingboy/archive/2007/06/18/787665.html