Debugging -- SessionID and ASP.Net

[alien2_51]

Insightful information indeed, is this documented anywhere..?


"Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
news:eeBzkQXUDHA.1864@TK2MSFTNGP11.phx.gbl...

> Not entirely.
> The SessionID is basically an in-memory cookie, and can survive as long as
> the browser is open.
> If the server gets the ID cookie back, but finds no session on the server,
> the session is created with the same ID.
> In other words, don't depend on the SessionID being different after a
> timeout.
>
> -Rob
>
> "alien2_51" <dan.billow@n.o.s.p.a.m.monacocoach.com> wrote in message
> news:ek60ZHUUDHA.2148@TK2MSFTNGP11.phx.gbl...

> > I have an ASP.NET app that serializes the data along with the sessionid
> > stored in the session into the database when the session times out it...
> > Provided the user does not close the browser(is where the previous

session

> > id is stored) they can reconnect to there session... The problem I'm

> seeing

> > is that the session id does not appear to change in my debugger.. I open

> up

> > perfmon connect to my appdomain add counter for active sessions, set my
> > session timeout to 1 min, when I see my counter drop to 0 sessions

active

> I

> > perform an action in the browser and whe I get to the break point I've

> set,

> > my session id is the same as it was before it timed out... Is this an

> issue

> > with the debugger attaching to the asp.net process...??
> >
> > Thanks,
> >
> > Dan
> >
> >

>
>

[Rob Teixeira [MVP]]

Yes. I have seen several articles on the issue, including something in the
knowledge base.
You might want to check the MS KB.

-Rob [MVP]

"alien2_51" <dan.billow@n.o.s.p.a.m.monacocoach.com> wrote in message
news:#BOgnofUDHA.2332@TK2MSFTNGP09.phx.gbl...

> Insightful information indeed, is this documented anywhere..?
>
>
> "Rob Teixeira [MVP]" <RobTeixeira@@msn.com> wrote in message
> news:eeBzkQXUDHA.1864@TK2MSFTNGP11.phx.gbl...

> > Not entirely.
> > The SessionID is basically an in-memory cookie, and can survive as long

as

> > the browser is open.
> > If the server gets the ID cookie back, but finds no session on the

server,

> > the session is created with the same ID.
> > In other words, don't depend on the SessionID being different after a
> > timeout.
> >
> > -Rob
> >
> > "alien2_51" <dan.billow@n.o.s.p.a.m.monacocoach.com> wrote in message
> > news:ek60ZHUUDHA.2148@TK2MSFTNGP11.phx.gbl...

> > > I have an ASP.NET app that serializes the data along with the

sessionid

> > > stored in the session into the database when the session times out

it...

> > > Provided the user does not close the browser(is where the previous

> session

> > > id is stored) they can reconnect to there session... The problem I'm

> > seeing

> > > is that the session id does not appear to change in my debugger.. I

open

> > up

> > > perfmon connect to my appdomain add counter for active sessions, set

my

> > > session timeout to 1 min, when I see my counter drop to 0 sessions

> active

> > I

> > > perform an action in the browser and whe I get to the break point I've

> > set,

> > > my session id is the same as it was before it timed out... Is this an

> > issue

> > > with the debugger attaching to the asp.net process...??
> > >
> > > Thanks,
> > >
> > > Dan
> > >
> > >

> >
> >

>
>