If you have an application set in IIS for the directory, the session
variables will not carry through. Like, example:
http://site/dir1/page1.asp contains:
session("test") = "test"
http://site/dir2/page1.asp contains:
response.write session("test")
That will work fine, by default. But if you go into your IIS manager and
create an application on dir2, you will lose the session variables in there.
Session variables are application based. If you don't need to have this
directory specified as a separate application, just remove it in IIS, and
your session variables will carry through.
Ray at work
"Gmmi" <al****@hotmail.com> wrote in message
news:06****************************@phx.gbl...
Ray for me it's not working. Due you know any reason? or
you are here just for fun.
Gmmi.
-----Original Message-----
Have you tested this to see if it's true?
Ray at work
"Gmmi" <al****@hotmail.com> wrote in message
news:30****************************@phx.gbl... Is it true that when your ASP application jump's from one Virtual Directory to another Virtual directory then you
cannot access session variables (which you created in
previous virtual directory pages).
Is there any way to work-around that? I don't want to
create the new session variables.
.
