Teach Yourself Visual Studio® .NET 2003 in 21 Days [Electronic resources] نسخه متنی

When I look at my Task Manager, there's a process called ASPNET_WP that consumes a bunch of memory. What is it?

The ASPNET_WP is the worker process that handles the processing of ASPX files for IIS. This application consumes more and more memory based on the number of users accessing your Web site. It has special permissions to access system files and directories because ASP.NET needs access to system resources on the IIS machine.

What's the deal with PostBack events? I see a lot of code in the Page_Load events of samples in the SDK that checks to see whether the page is being posted back.

The PostBack event is extre14mely important to understand. A Form_Load event occurs the first time a page is loaded to a client's browser. Most of the time, you're loading fields from a database or setting default values in controls. Because you can write pages that respond to multiple events on the server, the same page may be posted back to the server a number of times. So, by checking the IsPostBack property, you can avoid rerunning initialization code in events such as Form_Load. The common syntax for checking the IsPostBack property is

If Not Page.IsPostBack then
' Do some page initialization code, this is
' the first time the page has been called for this
' browser session
Else
' The page is being posted back so decide if you want
' to do anything there
End if

I've heard of cool things like caching and user controls. Where can I get more information about those topics?

In the .NET Framework SDK tutorials that install with Visual Studio .NET, look up the Caching topic under the How do I… section for ASP.NET. There are some great samples of implementing the different caching mechanisms in ASP.NET.