ASP.NET Supports Web Services - Examining the ASP.NET Page Class Process
(Page 4 of 5 )
ASP.NET pages begin as code in a text file with an .aspx extension. They reside within an IIS virtual directory created somewhere on your drive. All pages are instantiation classes derived from the Page class. The text file is transformed to an ASP.NET page when the client submits a request to the server. Then, the server renders the page to the client browser. All ASP.NET functionality lies primarily with the Page class.
Two separate methods exist for inheriting from the Page class. The first method facilitates adding the @Page directive to an .aspx file. The directive automatically makes available all page properties and methods for any code written on the page. The second method supports the code-behind feature and inherits from the Page class associated with a particular page by specifying either the Src or Inherits attribute.
<%@ Page Language=”vb” AutoEventWireup=”false” Codebehind=”RegisterForm.aspx.vb“ Inherits=”RegisterForm.WebForm1”%>
The best feature is that it allows ASP.NET to combine the code in the Web form’s .aspx file with the code in the code-behind class file. It then compiles both files to a single merged file called an assembly.
Next: Describing an ASP.NET Page’s Life Cycle >>
More ASP.NET Articles
More By Dwight Peltzer
