Okay, it’s an established fact that the Session object in ASP has no relation to the Session object in ASP.NET.

My question is this: If I have an ASP page, and it calls an ASPX page, which then does a Response.Redirect to another (or the same) ASP page, will the Session variables from the original ASP page be preserved in the final ASP page?  Does anybody know the answer, or do I need to experiment and see?

Hi,

U may use Database.. or We WebRequest and WebResponse..

http://comindotnet.blogspot.com/2009/03/sharing-session-and-cookies-in-com.html

chk the above link

daveh551:

My question is this: If I have an ASP page, and it calls an ASPX page, which then does a Response.Redirect to another (or the same) ASP page, will the Session variables from the original ASP page be preserved in the final ASP page?  Does anybody know the answer,

Yes, you can do that. Refer this..

Thanks to both of you for responding, but that's not the question I'm asking.  I know there are several ways to pass Session variables between ASP and ASP.NET, but that's not what I'm trying to do. I just want to know if the ASP Session variables will still be there when I navigate back to the ASP page after having been in an ASPX page.  If possible, I don't want to have to do anything or rewrite any of the 100 or so existing ASP pages to make that happen.

I did receive one affirmative answer on StackOverflow, so I think I'm okay.

As long as the intermediate .aspx page doesn't delete or modify the ASP session cookie (which it won't unless you're doing so intentionally), then you will be fine.  All session data is connected to the the session ID, which is stored in that cookie.

Also, cookie sharing/changing/deleting from one app to another can only happen if the apps are using the same cookie domains...

Yes the variables will be there in session until the session expires (this could happen if the session timed out, in your case if you did not make another .asp request in the specified timeout interval)