Is it OK to use __doPostBack()
or it is not recommended because it is generated from ASP.Net and we are not sure if they changed it in a next version of ASP.Net.

- 23,263
- 32
- 111
- 187
5 Answers
I would advice against it, since it's internal stuff of ASP.NET
and was never meant to be used directly.
Instead, what I'm doing when I need to "manually" trigger PostBack is adding hidden "server side" button with the proper OnClick:
<asp:Button id="btnDummy" runat="server" OnClick="Foo" style="display: none;" />
Then the JS is:
document.getElementById("<%=btnDummy.ClientID%>").click();
This way I don't care how post back happens, I just trigger the natural flow of events.

- 66,030
- 26
- 140
- 208
You should not call it directly. You should generate the javascript call by using functions in Page.ClientScript
such as:
This will ensure that it's always compatible.

- 36,141
- 15
- 83
- 142
They probably won't change it, but why call it directly?
I think it's a better strategy to trigger the event (a button click for example) and let the control trigger the postback.
I you do need to trigger the postback directly it's recommended to use the Page.ClientScript functions tenfour described.

- 28,949
- 7
- 62
- 78
I think its perfectly fine to use directly, and have used it without fail, its just a javascript function after all.

- 24,079
- 20
- 92
- 147
-
Yes, it's "just a javascript function", but the problem is that there is no *guarantee* that it will be present in a next version. – Hans Kesting Mar 27 '11 at 12:24
We use it all over the place and I can't imagine it would ever be stripped out of ASP.NET. I think the fake/hidden button method is just as hokie if not worse. If you use the fake button approach, then you get no option to pass in the __EVENTARGUMENT. I like using __EVENTARGUMENT to pass my data to the server better than creating hidden fields, because it would be more difficult for a hacker to compromise than simply posting back some hidden field to my page. I also don't like the idea of creating fields and controls on the page if they are not even going to be displayed. I am sure that the fake button approach is probably easier for a newbie coder to understand. That being said I am searching for a more elegant way to approach this, but still find myself calling
__doPostBack('%=UpdatePanel.ClientID%>','MyData')
in some cases.

- 108
- 12