It's the viewstate, a way of ASP.NET to store the page's state in the page itself, just google for "ASP.NET Viewstate"

---

This article seems to be the most usefull one: http://msdn2.microsoft.com/en-us/library/ms972976.aspx

Since we are talking about performance increase with this version of DNN is this really as optimized as it could be? I am especially concerned with the fact and I quote from the site above that "While view state enables state to be effortlessly persisted across postbacks, it comes at a cost, and that cost is page bloat. Since the view state data is persisted to a hidden form field, view state can easily add tens of kilobytes of data to a Web page, thereby increasing both the download and upload times for Web pages."

I see that this can be disabled in individual page with <%@Page EnableViewState="False" %>. Can't find anything about it in the documentation unfortunately to see if this is allowed or how to do it across the site and not just on main page.

ANy ideas, suggestions anyone?

Thanks,
Predrag