If you are talking a single page, ViewState is an option for persistence.
You can also create static variables, but you will have to key them to the
user. This means you either stick them in session or create your own
"session" mechanism. There are also other built in ASP.NET cache mechanism
(a search for "cache" and "asp.net" should yeield at least one article).
I would not be as fearful of session in ASP.NET as we were in traditional
ASP. It is far less dangerous, esp. if you think things through and only
store objects that have session scope.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************** *************** *************** ****
Think outside of the box!
*************** *************** *************** ****
"Robert" <Ro****@discuss ions.microsoft. comwrote in message
news:32******** *************** ***********@mic rosoft.com...
>I am trying to persist an instance specific object without using a session
object. Is this possible?
For example:
Class object: Car
Properties: Make, Model
Car.Make = Ford
Car.Model = F150
I would like to persist the object across postbacks without using a
session
object. Or, if I do have to use a session object, what is the cleanest
mechinsim. Right now I save the object in the session after each property
change.