Search:   Namespaces Discussions .NET v1.1 Feedback

Big Problems with .NET Framework 1.1 SP1 Messages   Related Types This message was discovered on microsoft.public.dotnet.framework. Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions. Post a new message to this list... Terry We have had 3 developers scrambling to fix problems with ASP.NET applications after installing Framework 1.1 SP1. In all cases the applications were working prior to installing the update. The first problem was that ASP.NET postback functions stopped working. Clicking a button on a page with a RequiredFieldValidator does nothing now. No postback. Replacing the "aspnet_client\system_web\1_1_4322\WebUIValidation.js" file with the old version seems to have fixed this problem. The second problem was with an ASP.NET Mobile Toolkit based application for cellular phones. The RedirectFromLoginPage method of the FormsAuthentication class stopped working. Again, replacing the client JavaScript with the earlier version solved the problem. We are still working on a fix for the third problem related to another ASP.NET application with several field validator objects in a form that will no longer post back. Be very cautious if you are installing this so-called (by Microsoft) "critical update." Reply to this message...        Mike (VIP) I've noticed that any web forms with validation controls will not postback. No validation controls - no problem. The jscript files seem to not be quite right. The controls still validate, but the form just won't submit. "Terry" wrote: [Original message clipped] Reply to this message...        Mike (VIP) Oh - I forgot - I rolled my version of the framework back to 1.1 pre sp1 and everything works fine. Just uninstall the framework and re-install 1.1 either the redistributable or the full sdk. Mike "Terry" wrote: [Original message clipped] Reply to this message...        William Stacey [MVP] (VIP) Did you test it first before rollout on production boxes? Just curious to see how many people do that without testing apps first. -- William Stacey, MVP "Terry" <Click here to reveal e-mail address> wrote in message news:Click here to reveal e-mail address... > We have had 3 developers scrambling to fix problems with ASP.NET applications [Original message clipped] Reply to this message...        Terry Yes. We found these problems in development on our development workstations. We halted all Framework updates as soon as we saw problem so no production servers were affected. But I must say that if Microsoft declares that an update is "Critical" on the Windows Update system, we are more likely to trust that it can be deployed without problems. There's a bit of good luck involved, because our network admins will sometimes install "Critical" updates and notify us after the fact. They take security seriously enough that they consider critical updates to be a necessity not an option. We generally review the descriptions first. Since this update does not appear to specifically address critical security issues, it *probably* would not have been deployed automatically. "William Stacey [MVP]" wrote: [Original message clipped] Reply to this message...        William Stacey [MVP] (VIP) In a previous live, I was admin on large unix and nt boxes. After some pain, I learned that no update should be applied before testing all critical apps. Anyway, you probably have this already, but create a Model environment that models production and Test environment. Admins should apply to Test first in there own play ground. After that works, apply to Model and have others sign off that all apps work before rolling to Production. That said, the roll to Production is not gaureenteed to work either, but at least you take the steps and reduce the odds. Just some random thoughts. Cheers. -- William Stacey, MVP "Terry" <Click here to reveal e-mail address> wrote in message news:Click here to reveal e-mail address... > Yes. We found these problems in development on our development workstations. [Original message clipped] Reply to this message...     System.Web.Security.FormsAuthentication System.Web.UI.MobileControls.RequiredFieldValidator System.Web.UI.WebControls.RequiredFieldValidator Ad MBR BootFX Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd. Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com