Hey Bill,

Just curious ... are you storing your Sessions in SQL Server?

~~Bonnie



>Hey Bonnie,
>
>No prob. Your answer was correct. I use more than one method for maintaining state but Session definitely the most. I just wanted to provide some additional info.
>
>Bill
>
>>Thanks for the correct answer, Bill. As I said, I wasn't 100% sure either way.
>>
>>~~Bonnie
>>
>>
>>
>>>Hi Chad,
>>>
>>>Alwaus good to just go ahead and add the [Serializable] attribute to classes that will be stored in Session. If you wind up using State Server or SQL Server to manage state, the objects have to serializable.
>>>
>>>Bill
>>>
>>>>Bonnie,
>>>>
>>>>Can any object be stored to a Session object and retrieved back as that object:
>>>>

>>>>Session["MyObject"] = myCustomObject;
>>>>

>>>>

>>>>CustomObject myCustomObject = (CustomObject)Session["MyObject"];
>>>>

>>>>Will I have to write special serialization/decoding code to make that happen?
>>>>
>>>>TIA,
>>>>Chad
>>>>
>>>>>Hi Chad,
>>>>>
>>>>>I haven't done much with Web apps lately, but when I was messing around with them a couple years back, I determined that the best way to persist data was with Session objects.
>>>>>
>>>>>~~Bonnie