I am a bit confused about the significance of the <form runat="server"> on a page, and its effect on Page and Control life cycles.
For long, I have eliminated any Postbacks or Viewstate from my web forms. I just use web forms to render (often very very complex) UI to the client (composed of server-side controls as well as ExtJs or jQuery widgets etc).
After the UI renders, all interaction with server is asynchronous through web-services or http handlers. So, lately I have started omitting the <form runat="server"> tage also from my web forms.
And to my surprise, the code has NOT broken. The life-cycle events are generated normally on all controls, they have access to normal ASP.NET processing pipeline, and they render perfect;y. As there are no Postbacks, I do not need ViewState or control events like click etc.
So, can somebody tell me if there's any material difference that <form runat="server"> would make in my scenario, or to ASP.NET page/control life-cycle??
View Complete Post