When the web server is stopped in an orderly fashion.

session is the state which holds the user info and helps to 
identify the user when the webpage is traversed(getting 
into next page of same website)...

ex: once u login in ur yahoomail, ur name is seen in ur 
inbox like "welcome raja"..
this is nothing bcoz of session info..

this session state is used to find long time idle and 
invoke automatic session state expire process...

Directive Specifies settings used by the page and user 
control compilers when they processes ASP.NET Web Forms 
page (.aspx) and user control (.ascx) files.


< @Page Attributes..... />  contain specific attributes for 
page
< @Import  Attributes...../> contain specific attributes 
for include libraries
< @Register   Attributes...../> contain specific attributes 
for control to be register for ther perticular page

sorry some syntex error was ther

i apoligies for that...

<% @Page Attributes..... %>  contain specific attributes 
for 
page
<% @Import  Attributes.....%> contain specific attributes 
for include libraries
<% @Register   Attributes.....%> contain specific 
attributes 
for control to be register for ther perticular page

select * from DATABASE_NAME where nos>='" & 15 & "' and 
nos<='" & 25 & "'

We can use the ROW_NUMBER Proberty from sql 2005

We can easily get the data's via roll numbers

You should configure exception management settings within 
your application's Web.config file. The following is an 
example of the exception settings in a Web.config file. 

< customErrors defaultredirect="http://hostname/error.aspx" 
mode="On"/>  
  < error statuscode="500" redirect="/errorpages/
servererror.aspx" />
  < error statuscode="404" redirect="/errorpages/
filenotfound.htm" />
< /customErrors>

edit item template fires when row index mathes editindex.
Because it is a template we can write all the controls and 
databinding expressions as demanded by the application

using querystring

Through Requested.querystring we can send the value from 
one page to another Page

We can also use cross post back property ofASP.NET 2.0

eg: 

1. Specify the ListBox as

<asp:ListBox ID="ListBox1" runat="server"            >
            <asp:ListItem Value="1" Text="1st Option" />
            <asp:ListItem Value="2" Text="2nd Option" />
            <asp:ListItem Value="3" Text="3rd Option" />
        </asp:ListBox>

2. Add this code in the default.aspx(.cs)

   public ListBox TheListBox
    {
        get
        {
            return ListBox1;
        }
    }
    protected void Page_Load(object sender, EventArgs e)
    {
        //Generate the cross-page postback script
        PostBackOptions options = new PostBackOptions
(ListBox1);
        //This will trigger correct script generation
        options.ActionUrl = "secondPage.aspx";

        //Add it to onchange attribute if the ListBox
        string s = 
Page.ClientScript.GetPostBackEventReference(options);
        ListBox1.Attributes["onchange"]=s;

    }

3. Then on secondPage.aspx

3.1 In aspx

<%@ PreviousPageType VirtualPath="~/Default.aspx"   %>

3.2 in Page_Load of the secondPage.aspx(.cs)

protected void Page_Load(object sender, EventArgs e)
    {
        if (PreviousPage != null && 
PreviousPage.IsCrossPagePostBack)
        {
            Response.Write("You selected " + 
PreviousPage.TheListBox.SelectedValue   );
        }
    }

page init

It is an event occured just before render.After that the
page  is rendered into HTML.

For every request to .aspx page the ASP.NET work processor
will create a new instance of the corresponding page class
object, once the request is executed the object of page
class is destroyed automatically, the page object life cycle
is controlled by its page life cycle events those are:
 1 page_Init
 2 page_Load
 3 page_Prerender
 4 Page_Unload
Page_Prerender: After page executed and before rendering the
output values to the the requested browser this event executes