計算機外文翻譯--asp.net 頁面對象模型

1、中文 中文 4150 字畢業(yè)論文(設計)英文翻譯材料學院: 計算機科學學院 專業(yè)： 自動化 年級:2011 學生姓名: 學號: 指導教師姓名: 職稱: 講師 The type of the HTTP handler for a particular page depends on the URL. The first time the URL is invo

2、ked, a new class is composed and dynamically compiled to an assembly. The source code of the class is the outcome of a parsing process that examines the .aspx sources. The class is defined as part of the namespace ASP an

3、d is given a name that mimics the original URL. For example, if the URL endpoint is page.aspx, the name of the class is ASP.Page_aspx. The class name, though, can be programmatically controlled by setting the ClassName a

4、ttribute in the @Page directive.The base class for the HTTP handler is Page. This class defines the minimum set of methods and properties shared by all page handlers. The Page class implements the IHttpHandler interface.

5、Under a couple of circumstances, the base class for the actual handler is not Page but a different class. This happens, for example, if code-behind is used. Code-behind is a development technique that insulates the code

6、necessary to a page into a separate C# or Microsoft Visual Basic® .NET class. The code of a page is the set of event handlers and helper methods that actually create the behavior of the page. This code can be define

7、d inline using the tag or placed in an external class—the code-behind class. A code-behind class is a class that inherits from Page and specializes it with extra methods. When specified, the code-behind class is used as

8、 the base class for the HTTP handler.The other situation in which the HTTP handler is not based on Page is when the configuration file of the application contains a redefinition for the PageBaseType attribute in the sect

9、ion.The PageBaseType attribute indicates the type and the assembly that contains the base class for page handlers. Derived from Page, this class can automatically endow handlers with a custom and extended set of methods

10、and properties.The Page LifecycleOnce the HTTP page handler class is fully identified, the ASP.NET run time calls the handler's ProcessRequest method to process the request. Normally, there is no need to change the i

11、mplementation of the method as it is provided by the Page class.This implementation begins by calling the method FrameworkInitialize, which builds the controls tree for the page. The method is a protected and virtual mem

12、ber of the TemplateControl class—the class from which Page itself derives. Any dynamically generated handler for an .aspx resource overrides FrameworkInitialize. In this method, the whole control tree for the page is bui

13、lt.Next, ProcessRequest makes the page transit various phases: initialization, loading of view state information and postback data, loading of the page's user code and execution of postback server-side events. After

14、that, the page enters in rendering mode: the updated view state is collected; the HTML code is generated and then sent to the output console. Finally, the page is unloaded and the request is considered completely served.