I have run into this enough that I no longer try to "optimize" my pages by
limiting the type of Session for each.
On some pages you can have full access to the Session while on others you
can set it to None or ReadOnly which is a minor performance improvement.
Whenever I went beck to edit those pages and I changed the code to use
Session it would fail. Then I would spend 10 minutes trying to figure out
why when I was the dope that had turned it off.
Hopefully, that is all you did too!
--
Joe Fallon
"Roy" <ro**********@gmail.com> wrote in message
news:11*********************@g14g2000cwa.googlegro ups.com...
I don't have your answer Lucas, but I'd like to hear what it is all the
same. I've run into this same problem myself. Are there any thorough
sites online that have in-depth info on the Session object?
For instance, if I set a session variable on page1, and someone clicks
a button which uses a Response.Redirect to send them to page2, why is
it that the session variable is no longer recognized as being set? The
compiler errors out on me. I assume it's because Response.Redirect is
not a good method of "linking" pages together into a session? If so,
then what is? Not trying to hijack this thread, I just think there's
skimpy info on the web concerning session objects (what makes life a
little more interesting for me is I don't have access to VS.NET)...