web forms flow

[c676228]

Hi all,
In traditional asp form, there is an action field in a form, any time the
page is valid, after click the submit button, the next page comes up based on
the value in the action field.
In asp.net, in the sumit_click sub, after validating the all the fields in a
form, do you always use response.redire ct or reponse.transfe r to go to the
next page, any other ways? what's the exactly difference or which one will be
better?
--
Betty

[Marina Levit [MVP]]

You would usually use Response.Redire ct. There is also Server.Transfer , but
that transfers the page without letting the client browser know, so the old
page would still be in the URL. In what I've seen, Response.Redire ct is a
pretty standard way to do it.

Also, submit_click would normally not just validate the fields - it would
also process the page. So you would not redirect to another page to have it
add a row in the database, for example. You would do it right in your event
handler, then redirect to the next page that is the logical next page in the
application.

"c676228" <be****@communi ty.nospam> wrote in message
news:6B******** *************** ***********@mic rosoft.com...

Hi all,
In traditional asp form, there is an action field in a form, any time the
page is valid, after click the submit button, the next page comes up based
on
the value in the action field.
In asp.net, in the sumit_click sub, after validating the all the fields in
a
form, do you always use response.redire ct or reponse.transfe r to go to the
next page, any other ways? what's the exactly difference or which one will
be
better?
--
Betty

[c676228]

Thank you, Marina, for your expert opinions.
Your reply give me a chance to ask you another question.
Let's assume I inserted a row of user data in the first web form, at that
time,
the web form doesn't present the credit card information for payment yet or
I still need a couple more forms to collect more user data.
after user input other data/credit card number etc. and the payment or
other insert action in other forms are failed, what should I do with the user
data I inserted to the tables in the former pages already?
--
Betty
"Marina Levit [MVP]" wrote:

You would usually use Response.Redire ct. There is also Server.Transfer , but
that transfers the page without letting the client browser know, so the old
page would still be in the URL. In what I've seen, Response.Redire ct is a
pretty standard way to do it.

Also, submit_click would normally not just validate the fields - it would
also process the page. So you would not redirect to another page to have it
add a row in the database, for example. You would do it right in your event
handler, then redirect to the next page that is the logical next page in the
application.

"c676228" <be****@communi ty.nospam> wrote in message
news:6B******** *************** ***********@mic rosoft.com...

Hi all,
In traditional asp form, there is an action field in a form, any time the
page is valid, after click the submit button, the next page comes up based
on
the value in the action field.
In asp.net, in the sumit_click sub, after validating the all the fields in
a
form, do you always use response.redire ct or reponse.transfe r to go to the
next page, any other ways? what's the exactly difference or which one will
be
better?
--
Betty

[Marina Levit [MVP]]

It all depends on your flow. In the case of the first page really only
collecting parts of the data, I wouldn't really insert that into a table
that holds only permanent custom requests. My example was pointing out that
typically a page will deal with its own data, and that was an example i
gave. I didn't mean to imply that it must always save its data to the
database even when it logically doesn't make sense to do so.

In your scenario it may make sense to hold on to the data in session
variables, redirect to the next page, etc, until you are ready to add data
to the database. In this case you are vulnerable to session time out
situations, although it may be acceptable for your application.

"c676228" <be****@communi ty.nospam> wrote in message
news:7D******** *************** ***********@mic rosoft.com...

Thank you, Marina, for your expert opinions.
Your reply give me a chance to ask you another question.
Let's assume I inserted a row of user data in the first web form, at that
time,
the web form doesn't present the credit card information for payment yet
or
I still need a couple more forms to collect more user data.
after user input other data/credit card number etc. and the payment or
other insert action in other forms are failed, what should I do with the
user
data I inserted to the tables in the former pages already?
--
Betty
"Marina Levit [MVP]" wrote:

You would usually use Response.Redire ct. There is also Server.Transfer ,
but
that transfers the page without letting the client browser know, so the
old
page would still be in the URL. In what I've seen, Response.Redire ct is a
pretty standard way to do it.

Also, submit_click would normally not just validate the fields - it would
also process the page. So you would not redirect to another page to have
it
add a row in the database, for example. You would do it right in your
event
handler, then redirect to the next page that is the logical next page in
the
application.

"c676228" <be****@communi ty.nospam> wrote in message
news:6B******** *************** ***********@mic rosoft.com...

> Hi all,
> In traditional asp form, there is an action field in a form, any time
> the
> page is valid, after click the submit button, the next page comes up
> based
> on
> the value in the action field.
> In asp.net, in the sumit_click sub, after validating the all the fields
> in
> a
> form, do you always use response.redire ct or reponse.transfe r to go to
> the
> next page, any other ways? what's the exactly difference or which one
> will
> be
> better?
> --
> Betty

[c676228]

OK, I understand you what you mean. For the session expiration issue.
I have heared I can change session expiration default value from 20 min.
to longer time in web.config file, what I don't know how yet.
--
Betty
"Marina Levit [MVP]" wrote:

It all depends on your flow. In the case of the first page really only
collecting parts of the data, I wouldn't really insert that into a table
that holds only permanent custom requests. My example was pointing out that
typically a page will deal with its own data, and that was an example i
gave. I didn't mean to imply that it must always save its data to the
database even when it logically doesn't make sense to do so.

In your scenario it may make sense to hold on to the data in session
variables, redirect to the next page, etc, until you are ready to add data
to the database. In this case you are vulnerable to session time out
situations, although it may be acceptable for your application.

"c676228" <be****@communi ty.nospam> wrote in message
news:7D******** *************** ***********@mic rosoft.com...

Thank you, Marina, for your expert opinions.
Your reply give me a chance to ask you another question.
Let's assume I inserted a row of user data in the first web form, at that
time,
the web form doesn't present the credit card information for payment yet
or
I still need a couple more forms to collect more user data.
after user input other data/credit card number etc. and the payment or
other insert action in other forms are failed, what should I do with the
user
data I inserted to the tables in the former pages already?
--
Betty
"Marina Levit [MVP]" wrote:

You would usually use Response.Redire ct. There is also Server.Transfer ,
but
that transfers the page without letting the client browser know, so the
old
page would still be in the URL. In what I've seen, Response.Redire ct is a
pretty standard way to do it.

Also, submit_click would normally not just validate the fields - it would
also process the page. So you would not redirect to another page to have
it
add a row in the database, for example. You would do it right in your
event
handler, then redirect to the next page that is the logical next page in
the
application.

"c676228" <be****@communi ty.nospam> wrote in message
news:6B******** *************** ***********@mic rosoft.com...
> Hi all,
> In traditional asp form, there is an action field in a form, any time
> the
> page is valid, after click the submit button, the next page comes up
> based
> on
> the value in the action field.
> In asp.net, in the sumit_click sub, after validating the all the fields
> in
> a
> form, do you always use response.redire ct or reponse.transfe r to go to
> the
> next page, any other ways? what's the exactly difference or which one
> will
> be
> better?
> --
> Betty

[Steven Cheng[MSFT]]

Hi Betty,

If you're using ASP.NET 2.0 to build the web application, you can also
consider the following means:

1. Use the cross-page post back to post one webform page to another webform
page, thus, the form data on previous form can be forwareded to the next
form page through buildin means. Also, cross-page post allow us to access
control collection in previous page from target page.

#Cross-Page Posting in ASP.NET Web Pages
http://msdn2.microsoft.com/en-us/library/ms178139.aspx

2. ASP.NET 2.0 provide a buildin Wizard web server control which can help
provide wizard/steps based work flow on single page. This is also a
possible approach(put all the input in single page).

#Wizard Web Server Control (Visual Studio)
http://msdn2.microsoft.com/en-us/lib...US,VS.80).aspx

Hope this also helps.

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

--------------------
| Thread-Topic: web forms flow
| thread-index: AcYjewl2EaALd/aURjWDwU9lh5MCF Q==
| X-WBNR-Posting-Host: 12.25.78.230
| From: "=?Utf-8?B?YzY3NjIyOA= =?=" <be****@communi ty.nospam>
| References: <6B************ *************** *******@microso ft.com>
<#u************ *@tk2msftngp13. phx.gbl>
<7D************ *************** *******@microso ft.com>
<eB************ **@TK2MSFTNGP14 .phx.gbl>
| Subject: Re: web forms flow
| Date: Fri, 27 Jan 2006 11:51:17 -0800
| Lines: 82
| Message-ID: <93************ *************** *******@microso ft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.publi c.dotnet.framew ork.aspnet
| NNTP-Posting-Host: TK2MSFTNGXA03.p hx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.p hx.gbl!TK2MSFTN GXA01.phx.gbl!T K2MSFTNGXA03.ph x.gbl
| Xref: TK2MSFTNGXA02.p hx.gbl
microsoft.publi c.dotnet.framew ork.aspnet:3741 23
| X-Tomcat-NG: microsoft.publi c.dotnet.framew ork.aspnet
|
| OK, I understand you what you mean. For the session expiration issue.
| I have heared I can change session expiration default value from 20 min.
| to longer time in web.config file, what I don't know how yet.
| --
| Betty
|
|
| "Marina Levit [MVP]" wrote:
|
| > It all depends on your flow. In the case of the first page really only
| > collecting parts of the data, I wouldn't really insert that into a
table
| > that holds only permanent custom requests. My example was pointing out
that
| > typically a page will deal with its own data, and that was an example i
| > gave. I didn't mean to imply that it must always save its data to the
| > database even when it logically doesn't make sense to do so.
| >
| > In your scenario it may make sense to hold on to the data in session
| > variables, redirect to the next page, etc, until you are ready to add
data
| > to the database. In this case you are vulnerable to session time out
| > situations, although it may be acceptable for your application.
| >
| > "c676228" <be****@communi ty.nospam> wrote in message
| > news:7D******** *************** ***********@mic rosoft.com...
| > > Thank you, Marina, for your expert opinions.
| > > Your reply give me a chance to ask you another question.
| > > Let's assume I inserted a row of user data in the first web form, at
that
| > > time,
| > > the web form doesn't present the credit card information for payment
yet
| > > or
| > > I still need a couple more forms to collect more user data.
| > > after user input other data/credit card number etc. and the payment
or
| > > other insert action in other forms are failed, what should I do with
the
| > > user
| > > data I inserted to the tables in the former pages already?
| > > --
| > > Betty
| > >
| > >
| > > "Marina Levit [MVP]" wrote:
| > >
| > >> You would usually use Response.Redire ct. There is also
Server.Transfer ,
| > >> but
| > >> that transfers the page without letting the client browser know, so
the
| > >> old
| > >> page would still be in the URL. In what I've seen, Response.Redire ct
is a
| > >> pretty standard way to do it.
| > >>
| > >> Also, submit_click would normally not just validate the fields - it
would
| > >> also process the page. So you would not redirect to another page to
have
| > >> it
| > >> add a row in the database, for example. You would do it right in
your
| > >> event
| > >> handler, then redirect to the next page that is the logical next
page in
| > >> the
| > >> application.
| > >>
| > >> "c676228" <be****@communi ty.nospam> wrote in message
| > >> news:6B******** *************** ***********@mic rosoft.com...
| > >> > Hi all,
| > >> > In traditional asp form, there is an action field in a form, any
time
| > >> > the
| > >> > page is valid, after click the submit button, the next page comes
up
| > >> > based
| > >> > on
| > >> > the value in the action field.
| > >> > In asp.net, in the sumit_click sub, after validating the all the
fields
| > >> > in
| > >> > a
| > >> > form, do you always use response.redire ct or reponse.transfe r to
go to
| > >> > the
| > >> > next page, any other ways? what's the exactly difference or which
one
| > >> > will
| > >> > be
| > >> > better?
| > >> > --
| > >> > Betty
| > >>
| > >>
| > >>
| >
| >
| >
|

[c676228]

Hi Steven,
Thank you so much. I am using asp.net 1.1. I didn't look at asp.net 2.0 yet.
I am still using visual studio.net 2003. If I download 2005. are all those
web server controls for asp.net 2.0 in vs.net 205?

--
Betty
"Steven Cheng[MSFT]" wrote:

Hi Betty,

If you're using ASP.NET 2.0 to build the web application, you can also
consider the following means:

1. Use the cross-page post back to post one webform page to another webform
page, thus, the form data on previous form can be forwareded to the next
form page through buildin means. Also, cross-page post allow us to access
control collection in previous page from target page.

#Cross-Page Posting in ASP.NET Web Pages
http://msdn2.microsoft.com/en-us/library/ms178139.aspx

2. ASP.NET 2.0 provide a buildin Wizard web server control which can help
provide wizard/steps based work flow on single page. This is also a
possible approach(put all the input in single page).

#Wizard Web Server Control (Visual Studio)
http://msdn2.microsoft.com/en-us/lib...US,VS.80).aspx

Hope this also helps.

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

--------------------
| Thread-Topic: web forms flow
| thread-index: AcYjewl2EaALd/aURjWDwU9lh5MCF Q==
| X-WBNR-Posting-Host: 12.25.78.230
| From: "=?Utf-8?B?YzY3NjIyOA= =?=" <be****@communi ty.nospam>
| References: <6B************ *************** *******@microso ft.com>
<#u************ *@tk2msftngp13. phx.gbl>
<7D************ *************** *******@microso ft.com>
<eB************ **@TK2MSFTNGP14 .phx.gbl>
| Subject: Re: web forms flow
| Date: Fri, 27 Jan 2006 11:51:17 -0800
| Lines: 82
| Message-ID: <93************ *************** *******@microso ft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.publi c.dotnet.framew ork.aspnet
| NNTP-Posting-Host: TK2MSFTNGXA03.p hx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.p hx.gbl!TK2MSFTN GXA01.phx.gbl!T K2MSFTNGXA03.ph x.gbl
| Xref: TK2MSFTNGXA02.p hx.gbl
microsoft.publi c.dotnet.framew ork.aspnet:3741 23
| X-Tomcat-NG: microsoft.publi c.dotnet.framew ork.aspnet
|
| OK, I understand you what you mean. For the session expiration issue.
| I have heared I can change session expiration default value from 20 min.
| to longer time in web.config file, what I don't know how yet.
| --
| Betty
|
|
| "Marina Levit [MVP]" wrote:
|
| > It all depends on your flow. In the case of the first page really only
| > collecting parts of the data, I wouldn't really insert that into a
table
| > that holds only permanent custom requests. My example was pointing out
that
| > typically a page will deal with its own data, and that was an example i
| > gave. I didn't mean to imply that it must always save its data to the
| > database even when it logically doesn't make sense to do so.
| >
| > In your scenario it may make sense to hold on to the data in session
| > variables, redirect to the next page, etc, until you are ready to add
data
| > to the database. In this case you are vulnerable to session time out
| > situations, although it may be acceptable for your application.
| >
| > "c676228" <be****@communi ty.nospam> wrote in message
| > news:7D******** *************** ***********@mic rosoft.com...
| > > Thank you, Marina, for your expert opinions.
| > > Your reply give me a chance to ask you another question.
| > > Let's assume I inserted a row of user data in the first web form, at
that
| > > time,
| > > the web form doesn't present the credit card information for payment
yet
| > > or
| > > I still need a couple more forms to collect more user data.
| > > after user input other data/credit card number etc. and the payment
or
| > > other insert action in other forms are failed, what should I do with
the
| > > user
| > > data I inserted to the tables in the former pages already?
| > > --
| > > Betty
| > >
| > >
| > > "Marina Levit [MVP]" wrote:
| > >
| > >> You would usually use Response.Redire ct. There is also
Server.Transfer ,
| > >> but
| > >> that transfers the page without letting the client browser know, so
the
| > >> old
| > >> page would still be in the URL. In what I've seen, Response.Redire ct
is a
| > >> pretty standard way to do it.
| > >>
| > >> Also, submit_click would normally not just validate the fields - it
would
| > >> also process the page. So you would not redirect to another page to
have
| > >> it
| > >> add a row in the database, for example. You would do it right in
your
| > >> event
| > >> handler, then redirect to the next page that is the logical next
page in
| > >> the
| > >> application.
| > >>
| > >> "c676228" <be****@communi ty.nospam> wrote in message
| > >> news:6B******** *************** ***********@mic rosoft.com...
| > >> > Hi all,
| > >> > In traditional asp form, there is an action field in a form, any
time
| > >> > the
| > >> > page is valid, after click the submit button, the next page comes
up
| > >> > based
| > >> > on
| > >> > the value in the action field.
| > >> > In asp.net, in the sumit_click sub, after validating the all the
fields
| > >> > in
| > >> > a
| > >> > form, do you always use response.redire ct or reponse.transfe r to
go to
| > >> > the
| > >> > next page, any other ways? what's the exactly difference or which
one
| > >> > will
| > >> > be
| > >> > better?
| > >> > --
| > >> > Betty
| > >>
| > >>
| > >>
| >
| >
| >
|

[Steven Cheng[MSFT]]

Thanks for your response Betty,

Yes, of course. If you're using VS 2005(or visual web developer express),
all the buildin ASP.NET 2.0 webcontrols are available in the ToolBox. Also,
some ASP.NET 1.1 compatible controls can also be used in aspx page(add them
manually) though they're not in toolbox by default. Anyway, you can have
a look at the wizard control in 2.0.

Hope this helps.

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[c676228]

Steven,
If I download VS 2005. Would my old asp.net application developed with .net
2003 will have any problems? Is it Ok to install both .net 2003 and VS 2005?
Thank you
--
Betty
"Steven Cheng[MSFT]" wrote:

Thanks for your response Betty,

Yes, of course. If you're using VS 2005(or visual web developer express),
all the buildin ASP.NET 2.0 webcontrols are available in the ToolBox. Also,
some ASP.NET 1.1 compatible controls can also be used in aspx page(add them
manually) though they're not in toolbox by default. Anyway, you can have
a look at the wizard control in 2.0.

Hope this helps.

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Juan T. Llibre]

You can install/run simultaneously both
VS 2003/.Net 1.1 and VS 2005/.net 2005.

No problem...

Just make sure your 1.1 apps are targeting the .net framework 1.1,
and that the 2.0 apps are targeting the .net framework 2.0.

You can do that in the "ASP.NET" tab of the Application's Properties in the IIS Manager.

Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
=============== =============== =====
"c676228" <be****@communi ty.nospam> wrote in message
news:F0******** *************** ***********@mic rosoft.com...

Steven,
If I download VS 2005. Would my old asp.net application developed with .net
2003 will have any problems? Is it Ok to install both .net 2003 and VS 2005?
Thank you
--
Betty "Steven Cheng[MSFT]" wrote:

Thanks for your response Betty,

Yes, of course. If you're using VS 2005(or visual web developer express),
all the buildin ASP.NET 2.0 webcontrols are available in the ToolBox. Also,
some ASP.NET 1.1 compatible controls can also be used in aspx page(add them
manually) though they're not in toolbox by default. Anyway, you can have
a look at the wizard control in 2.0.

Hope this helps.

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)