Re: Multi Page ASPX
From: nfedin (nfedin_at_programmer.net)
Date: 02/24/04
- Next message: Max: "Re: Default button - pressing Enter"
- Previous message: Craig Buchanan: "IIdentity casting problem"
- In reply to: Bill Smith: "Multi Page ASPX"
- Messages sorted by: [ date ] [ thread ]
Date: 24 Feb 2004 07:27:49 -0800
Posting back to the same page will probably be the best.
You could have everything on one page, but just hide what you don't
want the user to see. IIS will remember all the values for the hidden
fields but the user won't be able to see them.
You could also make three user controls, one for each page. It would
be just like above, but you would only have to show/hide the user
control instead of many input controls.
Hope this helps,
Neil
"Bill Smith" <no@spam.com> wrote in message news:<uWzHjtq#DHA.684@tk2msftngp13.phx.gbl>...
> I have a ASP webpage that creates user accounts. It currently use the format
> as follows.
>
> First Page:
> Input boxes that get Firstname and Lastname and Department etc.
> JavaScript Validation
> If correct posts information to Second Page
>
> Second Page:
> Makes a username, email address and displayname from given info then checks
> active directory to see if it exists. If it does exist it try's again until
> it finds a unused one.
> Then posts to third page:
>
> Third Page:
> Popup Window
> Displays the progress of creating the AD account and setting all the
> information.
> Once complete sends email and closes.
>
> I want to convert this to ASP.NET. The problem is I want to keep it very
> secure. Im reading I should posts each page to itself to get the most out of
> ASP.NET.
>
> Any ideas on the best way to go at this.
> Thanks
>
> Bill
- Next message: Max: "Re: Default button - pressing Enter"
- Previous message: Craig Buchanan: "IIdentity casting problem"
- In reply to: Bill Smith: "Multi Page ASPX"
- Messages sorted by: [ date ] [ thread ]