By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,499 Members | 1,321 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,499 IT Pros & Developers. It's quick & easy.

Page_load event cannot be fired

P: n/a
What is the possible error that occurs when the Page_load event is not triggered during execution.

In my page there's some basic server control. Is there any loops holes?
Nov 18 '05 #1
Share this Question
Share on Google+
1 Reply

P: n/a
Okay Session could be used across multiple worker processes but you have to set the session vars to be stored in State Server or Sql Server



There are a couple of ways to store information.

ViewState is most frequently used one cause there aren't excessive server overheads and the data is on client which is posted back

Storing in Session could be another way but again this would only work in a scenario where your application runs off a single aspnet worker process.

I had an interesting scenario where I did not want to keep the data in session (time out would sort of release the values) and I ended up creating a Cookie class to store some values (like say the selected item text for a dropdownlist and created a singleton which return client specific data using HttpContext.Current)

It works great but you have to sort of balance whether you really need that sort of implementation. Anything you do has atleast some overhead attached to it.

You could potentially even store it in database. But again you are looking at a db call to retrieve data.



From:Charlie [mailto:br*****]
Posted At: 07 March 2004 07:33
Posted To: aspnet
Conversation: Persisting State Information
Subject: Persisting State Information


Is there a way of persisting state information for a server control
without using ViewState? I'm currently using Page.Session() but I
don't think this is the best way. What's the preferred method?


Nov 18 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.