The event handlers all fire when they are supposed to...HOWEVER, an annoying glitch in Visual Studio can cause event handlers to become detached from time to time. This can be a minor inconvenience, or a major pain in the ass, as it was on my last page that had over 20 event handlers detaching all of a sudden.
As for the viewstate, the security measure you are talking about probably refers to the EnableViewStateMac setting, which can be set to false telling the system not to verify the integrity of the Viewstate. This opens an obvious security hole though. The work around presented in the link I sent is what we are currently trying, creating a manual key so that there is always something there for the system to authenticate against. > Usually then the viewstate can't be authenticated, it's just IIS > thinking it's been given a "different" viewstate" for the same page. I > "think" this is a security measure and can be disabled in the > web.config. I had some problems with it in the past (when getting pages > with Server.Execute). > > My biggest gripe with ASP.NET is the seemingly chaotic pattern that > event handlers execute. Probably because I haven't learned enough about > it, yet. :P > > E > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Sams Teach Yourself Regular Expressions in 10 Minutes by Ben Forta http://www.houseoffusion.com/banners/view.cfm?bannerid=40 Message: http://www.houseoffusion.com/lists.cfm/link=i:5:158839 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/5 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:5 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.5 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
