Session.isNewSession ...Unable to understand working.

Question

0.00/5 (No votes)

See more:

Hi All,

I am trying to work on an application where i am storing a string into Session like.

C#

Session["MyString"]

Further on the PageController Page.

I have code like below in Page Load.

C#

If(!Session.IsNewSession)
{
    if(user == null)
   {
     ////////////Do this...
    }

}
else
{
  if(Session["MyVariable"] !=null)     //Here I am always returning null :(
    {
     Delete();
     }
}

Can any body explains me that when the else part will be or should be executed?? and secondly why my

C#

Session["Variable"]

always getting null in return in else part?

Thanks :)

Posted 20-Dec-13 0:34am

VICK

Add a Solution

Comments

Ashish_Agrawal 20-Dec-13 6:46am

Where are you storing value into your session?

VICK 20-Dec-13 7:40am

when i entered a specific page, there i am calling a function n page load. and in that I have been storing that.

1 solution

Add a Solution

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2013-12-20T00:41:00

Solution 1

Um. Lets have a look at that code, shall we?

C#

If(!Session.IsNewSession)
{
...
}
else
{
  if(Session["MyVariable"] !=null)     //Here I am always returning null :(
  {
...
  }
}

So, you only directly try to use the Session variables if this is a new Session? When teh variables will default to null? And you are surprised that they are null...

Posted 20-Dec-13 0:41am

OriginalGriff

Comments

VICK 20-Dec-13 7:36am

Due to bad english, perhaps i could not have understood completely.. but I think you are saying that ELSE will come into work when the Session will be a new one and all old variables/sessions etc will default to null.. and hence i am getting null...

RIGHT??? :(

OriginalGriff 20-Dec-13 8:00am

Yes.
IsNewSession returns True for a new session, and "!" inverts that, so your else is only executed when you have a new (and hence empty) Session.

VICK 21-Dec-13 5:52am

hmm. dnt have much experience on sessions. well it means if i made two sessions during application run, like session["a"] & session["b"], so if application remains to idle the main HTTp session state will be null and hence both of my created session variables will be null as well... RiGHT?

OriginalGriff 21-Dec-13 6:38am

Yes. Remember, with seb sites, the Session is external to you application, and your application is "killed" as soon as the page data has finished going to the browser - and that means all your application data is gone as well unless you have stored it to the Session and / or cookies.

VICK 20-Dec-13 7:39am

Well. my problem is that I have to delete a record from db based on an ID, which I am storing in Session["MyVaraible"].
and I have a page controller class which consist of the code like i posted above.
every page of the application is inherited from this controller class.
So if i leave my application idle and it times out. i have seen that else comes into play that time.. and becuase mystored ID is null. so I am unable to delete the related record from DB.

is there any possible solution for that.?

Will be really glad, if you could guide me in bit detail.

NOTE: Have already Googled and checked MSDN. but unable to understand quitely..

:(

OriginalGriff 20-Dec-13 8:10am

Ah - If the problem is that the session is timing out, then that is a problem - you can't retrieve values from an expired session (the server memory has been recycled by that point)

Are you trying to delete a record if the session times out to save space or something?

VICK 21-Dec-13 5:48am

Sorry for being late. Actually I am storing logged in users of a specific module in a temporary table and deleting them when they leave that specific module by signing out. and further i want to delete them from that table if application session expires...

OriginalGriff 21-Dec-13 6:11am

Where is the temporary table stored?

VICK 21-Dec-13 6:30am

in SQL server 2008.

OriginalGriff 21-Dec-13 6:40am

You do realized that a Temporary Table in SQL is just that: temporary? And that it is destroyed when the connection is closed?

VICK 21-Dec-13 6:58am

sorry for the confusion...:(
well by temporary means the data which i am storing in that table is temporary and not the table itself. so it means my table will remain there in sql. but when user signout or application expires, user(s) records will be deleted from that table.

OriginalGriff 21-Dec-13 7:20am

You could use the Session_OnEnd event:
http://msdn.microsoft.com/en-us/library/ms178583.aspx
but there are caveats with that to do with the session type and so forth.

Personally? I wouldn't. I'd time-stamp the records in the table and use the timestamp to tell if the user should still be there or not. This would serve a dual purpose - it let you know if you should just ignore a user record without actually deleting it, and it lets you allow for failures - if the host computer or your application fails the SQL data is left in limbo "waiting" for a delete that never comes.

VICK 21-Dec-13 8:33am

got u Griff! :)

Thanks alot...

OriginalGriff 21-Dec-13 9:30am

You're welcome!

Session.isNewSession ...Unable to understand working.

1 solution

Solution 1

Add your solution here

Preview 0

Session.isNewSession ...Unable to understand working.

1 solution

Solution 1

Add your solution here

Preview 0

Existing Members

...or Join us