I'm confused (Viewstate and Context)

[Hugo Flores]

Hi,

I'm trying to pass information between pages. I'm trying to avoid using
QueryString and Session variables. I saw somewhere that I could use
contxt.Items.Add (combined with Server.Transfer) to store my
information and send it to another page. Some of my pages, either go to
other pages, or postback depending on the situation. When I began to
get confused was when I saw that I needed to store my variables on the
viewstate if I wanted to postback. So any answers to the next questions
could really help me understand all of this.

1. Isn't the context stored on the viewstate?
2. If that's the case, what would be the use of using the context
object if I'm going to end up storing everything on the viewstate to
get the info on postback, and also wouldn't I be duplicating my
viewstate when I and I reset my context variables, to do
Server.Transfer, because my viewstate already has that info.
3. What would be the best way to pass information, I'm only trying to
persist three variables, nothing more than that.

I know I must probably misunderstood the context object or the
viewstate. I really need somebody to get me out of my confusion.

Thanks

 

[Lucas Tam]

1. Isn't the context stored on the viewstate?

No, context items are sent as part of the server.transfer. After the
server.transfer, context items are disposed.

2. If that's the case, what would be the use of using the context
object if I'm going to end up storing everything on the viewstate to
get the info on postback, and also wouldn't I be duplicating my
viewstate when I and I reset my context variables, to do
Server.Transfer, because my viewstate already has that info.

You can't send viewstate between pages.

3. What would be the best way to pass information, I'm only trying to
persist three variables, nothing more than that.

Page A, use httpcontext to send the variables to Page B. In Page B, save
the variables to a viewstate variable which can be used during a
postback.

Or, use a session variable.

Or use a querystring.

There's nothing wrong with using a querystring - if you're querying
against public data (i.e. non secured data).