Update panels are great. Once you use them once you will use them everywhere. Until you realise that they can be slower (or seem slower) than a regular full postback. I use popup panels quite a bit and I think you get more flow in your web apps because you don't have to change pages quite as much.
One thing that's been bugging me with update panels though is the fact that I couldn't do a response.write from a button that was in an update panel e.g. send a pdf report to the browsers response to allow the user to view or save. If you tried to do this you would get an error like the following:
Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled.
After a bit of searching today I found one solution. Add the button into the update panels triggers section as a PostBackTrigger (as opposed to an AsyncPostBackTrigger you use when ChildrenAsTriggers is false).
Works a treat and allows me to keep the benfits of update panels.
Subscribe