EnableViewState

[Joe R.]

I use a couple of drop down lists in my application. Each
drop down list has less than 30 items(that I retrieved
from a SQL DB) and these items are very static. Do you
recommend using the EnableViewState for the same user
session or do you think that I should think about
caching? Which is better? Are there any security issues
that I need to be concerned about? My application is an
inquiry only application and the web SQL DB is a copy of
our production SQL DB (copied every night). Thanks.

 

[Victor Garcia Aprea [MVP]]

Hi Joe,

I think you're mixing your storage options a bit.

a) viewstate -- this storage is per-page and you usually may want to let it
enabled; only disable it after determining that a control will still work as
you want without mantaining viewstate.
b) session -- this storage is per-user
c) cache -- this storage is per-application

usually you will chose between b) or c) depending on the nature of the
retrieved data (which I can't determine by your post).

--
Victor Garcia Aprea
Microsoft MVP | ASP.NET
Looking for insights on ASP.NET? Read my blog:
http://obies.com/vga/blog.aspx
To contact me remove 'NOSPAM'. Please post all questions to the newsgroup
and not by private mail.