passing parameters from page to page

[only_me]

Having a bit of trouble here moving to .net. very familiar with the classic
ASP way of doing things but can't quite see the wood for the trees here in
..net

Classic ASP
On a form you have a number of form controls to accept user input, using the
the submit button passes those parameters across to next page in
request.form(keyname) fashion

..NET
Same as above but the norm, if you want to use form validation - which I
do, is that the form posts back to itself, so now in the button handler of
the equivelent of the Submit button I could do

If page.valid then
response.redirect (next_page)
end

But of course this won't pass across any form parmeters to the next , will
it

Whats the correct way to do this in .net ( I'm using VS)

I know you can change the .postbackurl of a button, but then I wouldn't get
my validation done, would I ?

Got a bit of mental block on this

TIA

 

[Mark Rae]

If page.valid then
response.redirect (next_page)
end

But of course this won't pass across any form parmeters to the next , will
it

Why do you need a second page?

 

[only_me]

Surely all .net sites aren't based on just one page ?

I'm converting this
https://www.guestmaster.com/onlinelive/frameset.asp?serialno=GM999999
to .net

Its a hotel booking site
page 1 collects/validates users input
if we have some availability, then page 2 will display the rooms types etc
available for further selection
then later on page 3 will collect users details etc to complete booking

 

[Paul Gielens]

public void Page_Load()
{
if (!IsPostBack)
{
Validate();
ProcessInput();
Response.Redirect();
}
}

Surely there are a number of options which is why advise you to get a copy
of Developing Web Application with Microsoft.NET
(http://www.microsoft.com/MSPress/books/6714.asp) and work your way through
chapter 3 Navigating Between Forms.

Best regards,
Paul Gielens

Visit my blog @ http://weblogs.asp.net/pgielens/
###

 

[Guest]

I know i have developed some that use only a couple of webforms. Look for
example at the City of North Vancouver website: www.cnv.org

ASP used a VB scripting language in which you had to divide the application
into manageable chunks of code, so one page used to post its results to the
next page that contained hundreds of script lines to handle the post action.
If you had a complex function (in a business or data layer) you would have
created for it a COM object.

ASP.NET, on the other hand, allows you to use programming languages that
employ Object Oriented Programming techniques, without the need to create COM
objects. The post back from each page needs not to be handled in a separate
page because you can arrange all of your functions in various classes that
are called from one page.

You might find this set of articles from MSDN helpful in migrating from ASP
to ASP.NET
http://www.msdn.microsoft.com/asp.net/learning/learn/migratingfromasp/default.aspx

 

[Mark Rae]

Surely all .net sites aren't based on just one page ?

No of course they aren't. But it's important to remember that ASP.NET is
very different from ASP, just as VB.NET is very very different from
VBScript.

Although I find the titles of these books extremely patronising, I'd suggest
you get the following:
http://www.amazon.co.uk/exec/obidos...8-1/ref=sr_8_xs_ap_i1_xgl/203-7938227-5328744

and read it from cover to cover. The main learning curve will be the .NET
Framework.

 

[only_me]

Ok thanks all

Seems I've got a lot more reading to do yet

a little knowledge eh ?

 

[Mark Rae]

Ok thanks all

Seems I've got a lot more reading to do yet

a little knowledge eh ?

The biggest piece of advice I can give you is not to consider ASP.NET as the
next version of ASP, and *especially* not to consider VB.NET as the next
version of VB6, let alone VBScript.

 

[Ken Cox]

http://authors.aspalliance.com/kenc/passval.aspx