I got second answer with IsPostBack... I know about it. It just solves the
issue that if you press a button on the form you don't want to do the same
actions that you do initial "arrival" to the page. It allows you to save
some calls to database and improve performance. In some cases you must use
it if you want to get new information from user.
Now ...
The problem is that if user clicks on the "Back" <-- button on the browser
then usually you get cash of the page that was saved by browser. (Am I wrong
about it? At least this is what I and my clients see). Really what I want to
get is updated version of the page.
Let say you have Product Information page that shows you basic information
about product. You have update functionality on a different page "Update
product information". Let say for sake of discussion after you update
product information you stay on the same page and don't redirect to Product
Information page. Now user wants to see product information page he /she
clicks on the "Back button on the browser (may be two times in my scenario)
and sees the page with old information (then client calls me and tells me
about a bug and I have to tell him/her to refresh the page. After few calls
the get the idea and I am off the hook.)
Can I do anything so the page will update after a user clicks on "Back"
button?
Again Thank you.
Shimon.
"Shimon Sim" <es*****@att.net> wrote in message
news:OR**************@TK2MSFTNGP10.phx.gbl...
Hi,
Every time I write ASP.NET application I have the same problem - Back
button on the browser is my enemy. I have to tell client avoid using
"Back" button and if you use it make sure to refresh the page to latest
information.
I decided to pay information to application on the web and I see that some
sites don't have those issues. Like I used some forum site that uses PERL
(files with ext. pl) and Back button from browser gets new updated page
everytime.
Can I do anything about this in ASP.NET?
Thanks,
Shimon.