_VIEWSTATE is toooooo big
-
HiHo okay... i got a dynamic generated Page... and there is the VieState hidden Field in the HTML Source passed to the user... okay okay..its needed - but is there a way to shrink the size of this viewstate without loosing features...maybe cacheing it on the server itself ? mfG. Daniel Kirstenpfad
-
HiHo okay... i got a dynamic generated Page... and there is the VieState hidden Field in the HTML Source passed to the user... okay okay..its needed - but is there a way to shrink the size of this viewstate without loosing features...maybe cacheing it on the server itself ? mfG. Daniel Kirstenpfad
"View" is what your client gets to see... So view state information has to go to client weather you maintain it on server, in a cookie or some remote machine... Consider the following: - use plain html controls as far as possible e.g: If you dont want to enable/disable or hide/show a button then use instead of - If you must you asp controls then try setting viewstate property of controls to false (wherever possible) Happy Programming -- Sumeet
-
"View" is what your client gets to see... So view state information has to go to client weather you maintain it on server, in a cookie or some remote machine... Consider the following: - use plain html controls as far as possible e.g: If you dont want to enable/disable or hide/show a button then use instead of - If you must you asp controls then try setting viewstate property of controls to false (wherever possible) Happy Programming -- Sumeet
Hi Sumeet, I have also observed this. My screens have multiple tables and for showing different screens like first editable screen and next confirm screen, I do a jugglery like hiding the second table first, showing the first one and reverse in the confirmation screen. Perhaps this comes handy so that you need not manually prefill values if the user goes somewhere and comes back. Perhaps if the number of controls in any of the tables in some of the screens exceed, the ViewState value exceeds too much. Once I copied the ViewState value, and checked how much it contained. It was 25.4K Could you suggest some optimal ways of using ViewState, without it getting swollen like this. Deepak Kumar Vasudevan http://deepak.portland.co.uk/
-
Hi Sumeet, I have also observed this. My screens have multiple tables and for showing different screens like first editable screen and next confirm screen, I do a jugglery like hiding the second table first, showing the first one and reverse in the confirmation screen. Perhaps this comes handy so that you need not manually prefill values if the user goes somewhere and comes back. Perhaps if the number of controls in any of the tables in some of the screens exceed, the ViewState value exceeds too much. Once I copied the ViewState value, and checked how much it contained. It was 25.4K Could you suggest some optimal ways of using ViewState, without it getting swollen like this. Deepak Kumar Vasudevan http://deepak.portland.co.uk/
Hello Deepak, I think your problem is somewhat different. Can you elaborate more... otherwise.. Consider using template fields in such cases. Make your design simpler using template data holders. Regards Sumeet Happy Programming -- Sumeet
-
"View" is what your client gets to see... So view state information has to go to client weather you maintain it on server, in a cookie or some remote machine... Consider the following: - use plain html controls as far as possible e.g: If you dont want to enable/disable or hide/show a button then use instead of - If you must you asp controls then try setting viewstate property of controls to false (wherever possible) Happy Programming -- Sumeet
Well; i fixed my problem by using sessionstate Stuff... but there another problem just poped-off.... iam saving the very big datatable i´m displaying into the sessiondata Object. Okay.. iam restoreing it... but it seems that the sessionstate object does not make any difference between users. In fact every user opening my WebForm just gets the datatable of the last user.... does anybody know how to treat this problem ? mfG. Daniel Kirstenpfad
-
Well; i fixed my problem by using sessionstate Stuff... but there another problem just poped-off.... iam saving the very big datatable i´m displaying into the sessiondata Object. Okay.. iam restoreing it... but it seems that the sessionstate object does not make any difference between users. In fact every user opening my WebForm just gets the datatable of the last user.... does anybody know how to treat this problem ? mfG. Daniel Kirstenpfad