In old school ASP if I wanted to keep my querystring clean, I would pass values from page to page via hidden inputs. I currently use the ViewState (aka "State Bag") to pass values back to the same page. However, this does not work when navigating to another page.

Official MS documentation suggests creating a custom property on the originating page, and then inheriting it on the receiving page (I'm pretty sure). This seems convoluted to me. Is there a simple solution?

The viewstate state bag only exists on one page instance. I'm not sure what MS is talking about with that stuff as one page can never see an instance of another page so you would therefore not be able to access another page's property and get anything useful from it. The simplest solution to this necessity is to use the session object as you would have in classic ASP.

Peter
------------------------------------------------------
Work smarter, not harder.

I can also just go and place values in the Querystring as well - it just seems like so much overkill to use the Session for that; I miss the old hidden inputs. :(

In God we trust, everything else we test.

Well, never say never. You *can* do that when you're using Server.Transfer:

http://authors.aspalliance.com/kenc/passval.aspx

http://msdn.microsoft.com/library/de...FormsPages.asp

Cheers,

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.