Learn Windows Azure Next Tuesday (Dec 13th):
As some of you might know, Scott GU have spent much of my time the last 6 months working on Windows Azure – which is Microsoft’s Cloud Computing Platform (I also continue to work on ASP.NET, .NET, VS and a bunch of other products).
Next Tuesday, Dec 13th we’ll be holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event either by watching it streamed LIVE online, or by attending in person (on the Microsoft Redmond Campus). Both options are completely free.

Learn Window Azure Event

During the Learn Windows Azure event attendees will learn how to start building great cloud based applications using Windows Azure.
I’ll be kicking off the day with a 90 minute keynote that will provide an overview of Windows Azure, during which I’ll explain the concepts behind it and the core features and benefits it provides. I’ll also walkthrough how to build applications for it using .NET, Visual Studio and the Windows Azure SDK (with lots of demos of it in action).
We’ll then spend the rest of the day drilling into more depth on Cloud Data and Storage, how to use the Visual Studio Windows Azure Tools, how to Build Scalable Cloud Applications, and close off with an Q&A panel with myself, Dave Campbell and Mark Russinovich.

Register Now for Free

The free Learn Windows Azure event will start at 9am (PST) on Dec 13th. You’ll be able to watch the entire event live on Channel9 or attend it in person. Both options are completely free.

• Register now to watch online or attend the event in person for FREE

ASP.NET Session state provides a place to store values that will persist across page requests.  Values stored in Session are stored on the server and will remain in memory until they are explicitly removed or until the Session expires.


C#

    Session["Name"] = "Hrishi"; // or Session.Add ("Name","Hrishi"); // retrievingstring

    Name = (string)Session["Name"];

By default the Session will be created within the same process that your web site runs in (InProc).  This is controlled by a setting in the web.config file:

    <sessionState mode="InProc" />

Although running the Session In Process is very convenient,  it does mean that all Session values will be lost whenever the application recycles (such as when deploying updates) .  There are alternate modes you can use that will allow the Session state to survive even when the application recycles.


    * Off - No session state will be stored
    * InProc - (The Default) Session state exists within the process the web is using
    * StateServer - Session data is sent to the configured stateserver service
    * SQLServer - Session data is store in the configured sql server database

Both the StateServer mode and the SQLServer mode allow Session state to survive an application recycle.  But, when storing reference type objects (such as class instances), they can only be stored to StateServer or SQLServer if they have been marked with the Serializable attribute.

An important consideration for using Session state is that the Session does expire.  By default, if a user does not access their Session data within 20 minutes (by default), the Session will expire and all items that had been stored in the Session will be discarded. Because of this, it is important to check the object that is returned from the Session to see if it exists or if it is null before you try to work with it. For example

object sessionObject = Session["someObject"];
if (sessionObject != null) {
 myLabel.Text = sessionObject.ToString();
}

The Session Timeout is adjustable through a web.config setting but increasing the timeout value can put memory pressure on your server that may be undesirable

     <sessionState timeout="number of minutes" />

Reference : MSDN