Ch.1 Application And Page Frameworks

Front 1

One of the major complaints about Visual Studio .NET 2002 and 2003

Back 1

One of the major complaints about Visual Studio .NET 2002 and 2003 is that it forced you to use the codebehind
model when developing your ASP.NET pages because it did not understand the code-inline model.

Front 2

To build an ASP.NET page inline instead of using the
code-behind model

Back 2

To build an ASP.NET page inline instead of using the
code-behind model, you simply select the page type from the Add New Item dialog and make sure that
the Place Code in Separate File check box is not selected.

Front 3

It is important to note that the more preferred method is

Back 3

It is important to note that the more preferred method is the code-behind model rather
than the inline model. This method employs the proper segmentation between
presentation and business logic in many cases.
presentation and business logic:
.aspx.vb /.aspx

Front 4

The .aspx page using this ASP.NET 4 code-behind model has some attributes in the Page directive that
you should pay attention to.

Back 4

CodeFile attribute
Inherits attribute

Front 5

A directive is written in the following format:

Back 5

<%@ [Directive] [Attribute=Value] ... %>

Front 6

P.10

Back 6

Table 1-4 summarizes the attributes available through the @Page directive

Front 7

if you want to initiate some action when
the end user clicks a button on your Web page, you create a button-click event in your server-side code

Back 7

Protected Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click
Label1.Text = TextBox1.Text
End Sub

Front 8

The following list shows you all the page events you could use.

Back 8

➤➤ AbortTransaction
➤➤ CommitTransaction
➤➤ DataBinding
➤➤ Disposed
➤➤ Error
➤➤ Init
➤➤ Load
➤➤ PreRender
➤➤ Unload
➤➤ InitComplete: Indicates the initialization of the page is completed.
➤➤ LoadComplete: Indicates the page has been completely loaded into memory.
➤➤ PreInit: Indicates the moment immediately before a page is initialized.
➤➤ PreLoad: Indicates the moment before a page has been loaded into memory.
➤➤ PreRenderComplete: Indicates the moment directly before a page has been rendered in the browser.

Front 9

If you create an ASP.NET 4 page and turn on tracing, you can see the order in which the main page events
are initiated. They are fired in the following order:

Back 9

1. PreInit
2. Init
3. InitComplete
4. PreLoad
5. Load
6. LoadComplete
7. PreRender
8. PreRenderComplete
9. Unload

Front 10

A postback

Back 10

A postback is just that — a posting back to the same page. The postback contains all the form
information collected on the initial page for processing if required.

Front 11

IsPostBack property of the Page class

Back 11

Because of all the postbacks that can occur with an ASP.NET page, you want to know whether a request
is the "first instance" for a particular page or is a postback from the "same" page. You can make this check by
using the IsPostBack property of the Page class, as shown in the following example:

If Page.IsPostBack = True Then
' Do processing
End If
"or"
If Not Page.IsPostBack Then
' Do processing
End If

Front 12

To get at a particular control’s value that is
carried over from the previous page

Back 12

To get at a particular control’s value that is
carried over from the previous page, you simply create an instance of that control type and populate this
instance using the FindControl() method from the PreviousPage property

Front 13

IsCrossPagePostBack

Back 13

in Page2.aspx The IsCrossPagePostBack property enables you to check whether the request is from Page1.aspx