Author: Dflying Chen ( http://dflying.cnblogs.com/ )
The emergence of Microsoft ASP.NET Atlas has almost subverted the entire traditional ASP.NET development concept. In theory, the most "pure" Atlas application will move all presentation layers to the client, and the server only provides the client Services required. So far, this client-side programming model does not have strong IDE support (think about how painful it is to write and debug JavaScript...), and considering that there are still many existing ASP.NET programs, and development Personnel also require some adaptation/learning time. In this way, while Atlas provides a pure client-oriented programming model, it also allows control developers to develop Atlas components in the form of server-side controls, so that traditional ASP.NET developers will not feel any difference when developing. It will also receive Visual Studio's design-time support, compile-time checking and other features, which smooths the learning curve for program developers.
Most of Atlas's server-side controls can be provided in the form of Extenders. The so-called Extenders, as the name suggests, are components that extend the functions and behaviors of existing controls. For example, add autocomplete function to the existing TextBox control, add confirmation dialog box to the existing Button control, etc. The Control Toolkit officially released by Atlas is a collection of several such Extenders. You can go here: "Atlas" Control Toolkit update release (Version 1.0.60504.0), and Atlas Control ToolKit release for more detailed information.
For this very common need to develop Extender, Atlas provides us with an Extender base class and the corresponding Project Template in Visual Studio. In this series, let’s learn together how to develop our custom Extender by using Atlas’ Extender base class and the corresponding Project Template in Visual Studio.
Throughout the series, I will explain the complete development process of a control. The function of the Extender I chose here is to use AJAX to verify in real time whether the user name is registered when the user fills in the registration information. A detailed introduction to this function As for the implementation of client-side Atlas Behavior, please refer to: Using ASP.NET Atlas to develop a custom Behavior that verifies whether the user name is registered in real time. I recommend friends who are interested in this series to read this article and understand the concepts in it, which will save a lot of time in future development.
Before developing this control, we need to install the following components/assemblies:
Atlas April CTP, please refer to: ASP.NET Atlas April CTP release, of course, you can only use the Atlas.dll, but I still recommend that you install Atlas Web Site's Template, so you can test your controls in real time during the development process.
Atlas Control Toolkit, please refer to: "Atlas" Control Toolkit update release (Version 1.0.60504.0), and Atlas Control ToolKit release. Download and run the self-extracting file AtlasControlToolkit.exe. You will get three directories, among which there are An AtlasControlExtender.vsi file. If you don’t want to manually create a Control project and numerous related files/references, it is best to run and install this Visual Studio Project Template (oh, of course, Visual Studio is still necessary).
If everything goes well, after the above two steps, you can see the Atlas Web Site Template when you create a new Web Site; you can also see the Atlas Control Project option when you create a new project.
By the way, the other two of the three directories after decompressing AtlasControlToolkit.exe:
The AtlasControlToolkit directory contains several Extenders provided by this Control Toolkit, all with source code (but no comments). This will be an indispensable sample program for you in the development process!
The SampleWebSite directory contains usage documentation and demonstration programs for the above Extender. You can learn how to use the developed Extender here.
All Extenders in this Control Toolkit and the provided Extender base classes comply with the Microsoft Permissive License agreement. This is a very loose agreement with basically no restrictions. Please see http://www.microsoft.com/resources/sharedsource/licensingbasics /permissivelicense.mspx .
(That’s it for today. I’m sorry to have written such a short article. I’m really a little tired... There will probably be about two or three more articles in this series. I wish you all a happy Children’s Day)