Ocean10000 - 5:24 pm on Mar 9, 2007 (gmt 0)

At first glance at the problem is that the developers didn't turn off viewstate for the div which they inserted the event html code from the database. Thus in effect they had the event html code for the event twice (once in the displayed code, and the second was encoded in viewstate).

I am assuming that that even page is static in that it is used only for a simple sign up page and the event data does not change, and that the actual text of the event data does not need to be posted back and used. The use of the Cache Object offered in Asp.net, could be used to store the event html on the server if its needed again for later page refreshes, to save it from being put into viewstate. I am going to assume the developers could use this same methodology a lot on the site to reduce the page bloat.