postbacktrigger

Greetings,

what is the benefit of the postbacktrigger within the updatepanel if it makes a a full postback?

since the updatepanel is specific for asynchronous postback!!!!

your help is highly appreciated

best regards.

Some controls aren't supported in update panels, so you may want to do a full postback if something happens that will cause that control to change. We had to do this with the report viewer..

PostBackTrigger control to enable controls inside anUpdatePanel to cause a postback instead of performing an asynchronous postback.

http://asp.net/AJAX/Documentation/Live/mref/T_System_Web_UI_PostBackTrigger.aspx

Thank you for the support.

so if some some controls needs to cause a full postback within updatepanel so what is the benefit in this case to use the updatepanel??

your help is highly appreciated

Best regards.

At one point a lot of the controls that aren't supported in update panels did work inside update panels, but as of the Beta releases, the update panels were changed, so it may have been to ease the transition for people who had been using previous version...as we had been doing..

There may also be some cases that other content in the update panel can be refreshed asynchronously, although it has been a while since I have worked a lot with the controls that aren't supported.

Thank you for the support

But i don't understand exactly what you say ,so you can give more details??

your help is highly appreciated

Best regards.

There were CTP releases generally monthly that were public a little over 6 months before the first Beta release. Around the second of the CTPs, the releases started to have good support in the forums and documentation, and the releases were able to be used in production websites. When Beta 1 came out, the asyncpostback changed with update panels. Upgrading to the Beta releases could take a lot of time because of the change. Most of our major issues were solved by using a different control. We ended up using the full post back in a web application we had, which was a very large page of about 5000 lines of code for the aspx and cs files. There were three different versions of that page, which all have nested update panels. In a couple of the nested panels we needed to have report viewers. All this was also live at the time that Beta 1 came out, and many different users were already used to the system, so we couldn't change it too much. Using the full postback trigger allowed us to have a button to make the report viewer visible while allowing everything else on the page to still update asynchronously.

Hopefully that helps.