I have a site that features some pages which do not require any post-back functionality. They simply display static HTML and don’t even have any associated code. However, since the Master Page has a <form runat="server"> tag which wraps all ContentPlaceHolders, the resulting HTML always contains the ViewState field, i.e:
What is the cause of this exception in ASP.NET? Obviously it is a viewstate exception, but I can’t reproduce the error on the page that is throwing the exception (a simple two TextBox form with a button and navigation links).
Every now and then (once every day or so) we’re seeing the following types of errors in our logs for an ASP.NET 3.5 application
One of the major reasons for using webforms is the ease of being able to maintain viewstate. I would like to build an asp.net mvc application so what options do I have for maintaining viewstate?
What different ways are Machine Keys useful in asp.net?
I think the following are correct but thought there may be more.
I have the following situation… In a certain View, the user must select the initial hour, the final hour and the weekday. But, I can’t save this informations to DB ’cause I need to save my whole page and I need the primary key of the primary table, but that’s not the point.
In asp.net pages, during postback, ViewState makes the data persistent. What makes the data persistent in ASP.net MVC? Answers: Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or … Read more
Can anybody help me out with this exception. I have tried couple of fixes but nothing worked. I am getting this exception only in IE(7, 8 and 9).
I wrote a ASP.NET Application and it run in IIS7 of a Server. If I open this webform in my Browser and show me the Sitecode I see this…
Problem with dynamic controls