Hi Brian, you can have your pages as user controls inside a container web
form page. You can either load them dynamically by placing the placeholder on
the container page or play around with the visible property of user controls.
You can keep track of the current page on a variable which can be persisted
on the viewstate or cache. In order to prevent the back button, try to set
the expiration of the page to 0.
Check out the issue tracker starter kit, which I think has a wizard.
"Brian" wrote:
I'm writing a .Net Web application. I'm trying to find out two things.
1) Once a user clicks a button that takes them to the next page, I don't
want them to be able go back to the previous page.
2) The only way I want them to be able to get to the 2nd and 3rd pages is
by going through the first page. I don't want them to be able to type the
URL of the 2nd page and go directly to it.
Any suggestions.
