Gain an understanding of the ASP.NET fundamentals with these links
This topic outlines the life cycle of ASP.NET applications, listing important life-cycle events and describing how code that you write can fit into the application life cycle.
An ASP.NET HTTP handler is the process that runs in response to a request made to an ASP.NET Web application. An HTTP module is an assembly that is called on every request that is made to your application.
ASP.NET includes several options that help you preserve data on both a per-page basis and an application-wide basis.
Using the features of the ASP.NET configuration system, you can configure all of the ASP.NET applications on an entire server, a single ASP.NET application, or individual pages or application subdirectories. You can configure features, such as authentication modes, page caching, compiler options, custom errors, debug and trace options, and much more.
The ASP.NET compilation architecture includes a number of features including multiple language support, automatic compilation, flexible deployment, and an extensible build system.
ASP.NET routing enables you to use URLs that do not have to map to specific files in a Web site. Because the URL does not have to map to a file, you can use URLs that are descriptive of the user's action and therefore are more easily understood by users.
Scott Hanselman introduces ASP.NET Friendly URLs - cleaner URLs, easier routing, and mobile views for ASP.NET Web Forms.