If I want the object be persisted across postbacks, is it a good idea to store Object in ViewState? Are there any better ideas? I am afraid the size of ViewState is too large…
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If I want the object be persisted across postbacks, is it a good idea to store Object in ViewState? Are there any better ideas? I am afraid the size of ViewState is too large…
If the object is too large, ViewState is a bad idea. Also there are other considerations regarding storing the information in the ViewState like security and how long you want the information to persist.
See ASP.NET State Management Overview for what other options you have.
Check ASP.NET State Management Recommendations to determine what to use in different scenarios.
I once stored a DataTable (facepalm) in the view state and was wondering why it took so much time load the page in a mobile browser. Storing it in session was MUCH faster because the page was not bloated with unnecessary objects.