Session.Abandon();
Response.Redirect("LogIn.aspx");
But, it seems that these are causing havoc when I go to run the website. By
havoc, I mean the website does not want to load. Either the 2 lines are not
correct or I am putting them in the wrong place.
Is there a better way to close it all down than these 2 lines? If these 2
lines are okay then where are they placed?
Thanks...John
> I have a masterpage that has a hyperlink in the header titled 'Log Out'.
> The
> intent is to have the user select this and it would end all sessions for
> all
> apps that were open and go back to the log in screen.
Firstly, there is only one Session object per instance of browser, and there
is only one Application object shared by all instances. Not quite sure what
you mean by "all sessions for all apps", though this may just be a question
of nomenclature...
> But, it seems that these are causing havoc when I go to run the website.
> By
> havoc, I mean the website does not want to load.
You'll need to describe in more detail exactly what happens or, more
accurately, what doesn't happen... When you're debugging, do you get as far
as the Page_Load event of the login page before the "havoc" starts...?
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
"JohnE" <Jo...@discussions.microsoft.com> wrote in message
news:0B089289-66AD-499B...@microsoft.com...
A question I do have is that when the LogOut is used with the 2 lines
posted, I can return back by using the browser's back button. How do I end
it all so if the users do use the back button (and I know some will), there
is nothing to go back to?
Thanks.
... john