I tried using Session.Abort() and Session.Clear() and used both of them
together and the session id still persists.
Thanks.
Don't know for Abort but Clear just clears the session variable...
--
"Andy G" <ajg...@iastate.edu> a écrit dans le message de
news:OEFe7RNA...@TK2MSFTNGP14.phx.gbl...
session.LCID gets or sets locale identifer for the session, u may want
to check it out too
Sharing makes All the Difference
--
Sent via .NET Newsgroups
http://www.dotnetnewsgroups.com
Abondon will not force ASP.NET to create a new session ID. Abondon calls
the Session_End and then the Session_Start, so really it doesn't do much
different than Clear.
I'm going to try using the session.timeout(0.00000001), whatever Dave
suggested below.
"Patrice" <nob...@nowhere.com> wrote in message
news:OqLWJXNA...@TK2MSFTNGP10.phx.gbl...
Using the below on the page load will force ASP.NET to get a new Session
variable. I tried to put this same code on a button click event and it
didn't work. I tried it checking the post back and then leaving it out,
didn't make a difference. So the question is, what can Page_Load do/have
access to that a button click event doesn't?
FORCE ASP.NET TO GET A NEW SESSION VARIABLE
If Not IsPostBack Then
Request.Cookies("ASP.NET_SessionId").Expires = Now
End If
Hope some of this helps you guys. Thanks for the help too.
-Andy
"Dave Johnson" <eshar...@gmail.com> wrote in message
news:%23IH1LSO...@TK2MSFTNGP12.phx.gbl...