Last post Feb 28, 2010 09:14 PM by psuphish05
Feb 28, 2010 04:46 PM|zoltac007|LINK
We have a website developed using VS 2005 coded in 2.0 Framework using C# code behind. When After we called our hosting company asking them to install the 3.5 SP1 update the site crashed with mulitple ViewState errors. They tried to uninstall the SP1 update.
No help. We deleted and restored the entire website with backup code from day before, no help. They uninstalled .Net and reinstalled both .Net and all website files - no help.
Finally they built a new server box used same backup - and we are running. We believe problem is caused by our website's 2.0 coding, DataKeys, Streamwriter calls and the code's dependence on viewstate. We were surprised at how catastrophic the failure
NEW PROBLEM - we lost our install of VS 2005 which was used to generate our code. Our disks are not compatible with our VISTA operating system so we can't install them. We installed the VS 2008 Professional Trial to get running again. MY CONCERN is -
if we use VS 2008 to administer our website 2.0 code, are we risking code changes that could again cause us to fail again. Framework 3.5 SP1 is not installed on this server.
Feb 28, 2010 08:38 PM|psuphish05|LINK
.NET 3.5 is still the 2.0 codebase library. You shouldn't encounter any issues with using VS 2008.
Hope this provides some insight.
Feb 28, 2010 08:46 PM|zoltac007|LINK
The issues are caused by SP1 for Framework 3.5. It appears to have something to do with the addition of a new variable which has been added to the Form Action. In our case it was a major issue and proven to be directly caused by the installation of the 3.5
Service Pack 1 on the server. No hosting company had never seen anything like it but did finally agree the culprit was in fact the SP 1. It smiply means that ViewState dependent 2.0 code has problems when it is recompiled with the SP1 installed.
It is real - cost us a small fortune and we will have to update our code.
Feb 28, 2010 09:14 PM|psuphish05|LINK
What was the error that you were seeing?
Are you explicitly setting the form action in the markup? I just did a quick search and I could see in the 3.5 SP1 release is that you can now set the form action for control over the postback URL. Whereas in previous versions the form action attribute
Also, they added the, RenderAllHiddenFieldsAtTopOfForm, which will place the hidden fields at the top of the form, when set to true, to prevent any postback issues prior to the whole page loading.
Here's Scott Hanselman's post of the 3.5 SP1 changes: