Check in your Web.config, that's where it is set. InProc is the default.
And if you haven't had any serialization warnings after putting custom
objects into session, then you're using InProc.
"Bilbo" <Bi***@cox.net> wrote in message
news:e$*************@TK2MSFTNGP11.phx.gbl...
Thanks for your response. How can I tell if I am using InProc?
Thanks.
"Marina" <so*****@nospam.com> wrote in message
news:O3****************@tk2msftngp13.phx.gbl... It only needs to be serializable if you using session state other then
InProc. If you are using InProc, you can place anything you want into
session.
"Bilbo" <Bi***@cox.net> wrote in message
news:eZ**************@TK2MSFTNGP10.phx.gbl... Hello,
I recently read that a class must support serialization in order for
it to be stored in the Session State. Before reading this I had been storing
a class to the Session State no problem (without serialization). The
class is simply a storage class and contains only primitive types....is it
necessary to serialize this object? If so, how do you go about serializing an
entire class?
Thanks much.