M
Martin
Hi,
In the scenario described by Scott Allen at
http://odetocode.com/Articles/421.aspx, he points out the issue of handling
server side validation failing on the source page of a cross page post back.
I would expect there would be a way of source page knowing it was executing
on behalf of the destination page (could be IsCrossPagePostBack==true &&
PreviousPage==null), and being able to abort/cancel the hand back to the
destination page, so that the source page was served back to the user with
relevant error messages and original data. However the call stack pretty
much comits a return to the destination page.
Does any one have a solution for managing this scenario?
Thanks
Martin
In the scenario described by Scott Allen at
http://odetocode.com/Articles/421.aspx, he points out the issue of handling
server side validation failing on the source page of a cross page post back.
I would expect there would be a way of source page knowing it was executing
on behalf of the destination page (could be IsCrossPagePostBack==true &&
PreviousPage==null), and being able to abort/cancel the hand back to the
destination page, so that the source page was served back to the user with
relevant error messages and original data. However the call stack pretty
much comits a return to the destination page.
Does any one have a solution for managing this scenario?
Thanks
Martin