D
Daves
I have a paired TextBox and Button on my masterpage for login, this way user
doesn't have to go to a special login page to do that - fewer clicks. The
trick is done via PostBackUrl and in the target page the TextBox's class is
built up again by this.PreviousPage.FindControl("textbox") ...
Obviously, in the background the previous aspx page is re-run to initialise
it's classes so that I can grab the entered value in the button's paired
TextBox. Fine - this works until some querystring value is required for that
previous page to run, let's say getting an ID for an item to fetch from
database. So an error occurs and boom... the application is down.
This must be a bug in asp.net? Has anyone come to workarounds?
doesn't have to go to a special login page to do that - fewer clicks. The
trick is done via PostBackUrl and in the target page the TextBox's class is
built up again by this.PreviousPage.FindControl("textbox") ...
Obviously, in the background the previous aspx page is re-run to initialise
it's classes so that I can grab the entered value in the button's paired
TextBox. Fine - this works until some querystring value is required for that
previous page to run, let's say getting an ID for an item to fetch from
database. So an error occurs and boom... the application is down.
This must be a bug in asp.net? Has anyone come to workarounds?