Dun understand why need to name the Session = something

Hi Sudipta,

 

I have the same thinking as you.  But then, when I don't enter anything, it doesn't return the hard coded name....

 

So, it puzzles me why having that 2 lines.

 

Could you please explain ?

 

Tks.

Hi,

 

Your code changes as below -

 

 

Now you can run SessionForm.aspx page and enter values and press submit.

It will go to Default2.aspx page.

 

If you try directly accessing Default2.aspx page, you will be redirected to SessionForm.aspx page.

 

That's how it works!

Hi 

AsPer your code You check in default2 page is the session is null 

 

if (Session["FirstName"] == null && Session["LastName"]==null)

 

if  Session is not found then only the HARDCode data will be set Other wise it takes data from session variable which is set in default1

Hi Midhun,

 

 

Could you edit my code and show me how it should be done in the right way?

 

Tks!

Hi,

 

Don't know from where you got this code. Anyways there is no need of hardcoding Session values there.

 

In normal cases (For example, an post login page), we check the value of session and if it is null, we just redirect to login page. 

 

I think the above example is only for demo purpose. 

Hi Sudipta,

 

I asked why we need this below part to be part of the code.

 

Session["FirstName"] = "Aspdotnet"

Session["LastName"] = " Suresh";

 

 

Kindly explain.

Hi Sudipta,

 

But, it doesn't make sense the hardcode the name since the name will change anyway.

 

Session["FirstName"] = "Aspdotnet"

 

Session["LastName"] = " Suresh";

 

Please explain why the hardcode part is for. Tks.

When you are working with an application on your computer, you open it, do some changes and then you close it. This is much like a Session. The computer knows who you are. It knows when you open the application and when you close it. However, on the internet there is one problem: the web server does not know who you are and what you do, because the HTTP address doesn't maintain state.

Solves this problem by creating a unique cookie for each user. The cookie is sent to the user's computer and it contains information that identifies the user. This interface is called the Session object.

The Session object stores information about, or change settings for a user session.

Variables stored in a Session object hold information about one single user, and are available to all pages in one application. Common information stored in session variables are name, id, and preferences. The server creates a new Session object for each new user, and destroys the Session object when the session expires.