Make Server.Transfer Postback

[kaburke]

Is there a way to make a page at the receiving end of a Server.Transfer
think that the request is a Postback? (When I say "think it is a Postback,"
I mean I want the page to go through the ENTIRE event sequence for a
postback, including LoadViewState, ProcessPostData, etc.) Even when
Sever.Transfer transfers a page to itself (i.e., Page A.aspx contains
Server.Transfer("A.apsx")) the request is seen as a first-time request, not
a Postback. Is there some way to fool/force the page into thinking the
request is a Postback and run through the entire event gambit, whether it is
from the same page or not?

To answer the inevitable question, "Why?" I have the following flow in my
application:

a.apsx -> b.aspx -> a.aspx

where b.aspx Server.Transfers to a.aspx. Upon return to a.aspx, I want the
form to pick up where it left off, so that the little side trip to b.aspx
doesn't interrupt the user experience.

Thanks,
--kaburke

[kaburke]

Alternatively, is there some way to force execution of the entire event
sequence (LoadViewState, ProcessPostData, etc.) even when the request is not
a Postback?

Thanks,
--kaburke

"kaburke" <ph**********@hotmail.com> wrote in message
news:YK%Me.202006$tt5.82500@edtnps90...

Is there a way to make a page at the receiving end of a Server.Transfer
think that the request is a Postback? (When I say "think it is a
Postback," I mean I want the page to go through the ENTIRE event sequence
for a postback, including LoadViewState, ProcessPostData, etc.) Even when
Sever.Transfer transfers a page to itself (i.e., Page A.aspx contains
Server.Transfer("A.apsx")) the request is seen as a first-time request,
not a Postback. Is there some way to fool/force the page into thinking the
request is a Postback and run through the entire event gambit, whether it
is from the same page or not?

To answer the inevitable question, "Why?" I have the following flow in my
application:

a.apsx -> b.aspx -> a.aspx

where b.aspx Server.Transfers to a.aspx. Upon return to a.aspx, I want the
form to pick up where it left off, so that the little side trip to b.aspx
doesn't interrupt the user experience.

Thanks,
--kaburke

[John Timney \(ASP.NET MVP\)]

why dont you just server.execute page b passing the data it needs to b, that
way page a will wait for page b to complete

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

"kaburke" <ph**********@hotmail.com> wrote in message
news:YK%Me.202006$tt5.82500@edtnps90...

Is there a way to make a page at the receiving end of a Server.Transfer
think that the request is a Postback? (When I say "think it is a
Postback," I mean I want the page to go through the ENTIRE event sequence
for a postback, including LoadViewState, ProcessPostData, etc.) Even when
Sever.Transfer transfers a page to itself (i.e., Page A.aspx contains
Server.Transfer("A.apsx")) the request is seen as a first-time request,
not a Postback. Is there some way to fool/force the page into thinking the
request is a Postback and run through the entire event gambit, whether it
is from the same page or not?

To answer the inevitable question, "Why?" I have the following flow in my
application:

a.apsx -> b.aspx -> a.aspx

where b.aspx Server.Transfers to a.aspx. Upon return to a.aspx, I want the
form to pick up where it left off, so that the little side trip to b.aspx
doesn't interrupt the user experience.

Thanks,
--kaburke

[kaburke]

Page b.aspx requires user interaction, so doesn't Server.Execute end up (in
this situation) behaving like Server.Transfer (i.e., isn't execution of
a.aspx ended when b.aspx is returned to client)?

Thanks,
--kaburke

"John Timney (ASP.NET MVP)" <ti*****@despammed.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...

why dont you just server.execute page b passing the data it needs to b,
that way page a will wait for page b to complete

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

"kaburke" <ph**********@hotmail.com> wrote in message
news:YK%Me.202006$tt5.82500@edtnps90...

Is there a way to make a page at the receiving end of a Server.Transfer
think that the request is a Postback? (When I say "think it is a
Postback," I mean I want the page to go through the ENTIRE event sequence
for a postback, including LoadViewState, ProcessPostData, etc.) Even when
Sever.Transfer transfers a page to itself (i.e., Page A.aspx contains
Server.Transfer("A.apsx")) the request is seen as a first-time request,
not a Postback. Is there some way to fool/force the page into thinking
the request is a Postback and run through the entire event gambit,
whether it is from the same page or not?

To answer the inevitable question, "Why?" I have the following flow in my
application:

a.apsx -> b.aspx -> a.aspx

where b.aspx Server.Transfers to a.aspx. Upon return to a.aspx, I want
the form to pick up where it left off, so that the little side trip to
b.aspx doesn't interrupt the user experience.

Thanks,
--kaburke

[Eliyahu Goldin]

Do you want b.aspx to run in the same browser window or in a different one?
In the latter case you could start another window on client side without any
postback in a.aspx.

Eliyahu

"kaburke" <ph**********@hotmail.com> wrote in message
news:YK%Me.202006$tt5.82500@edtnps90...

Is there a way to make a page at the receiving end of a Server.Transfer
think that the request is a Postback? (When I say "think it is a Postback," I mean I want the page to go through the ENTIRE event sequence for a
postback, including LoadViewState, ProcessPostData, etc.) Even when
Sever.Transfer transfers a page to itself (i.e., Page A.aspx contains
Server.Transfer("A.apsx")) the request is seen as a first-time request, not a Postback. Is there some way to fool/force the page into thinking the
request is a Postback and run through the entire event gambit, whether it is from the same page or not?

To answer the inevitable question, "Why?" I have the following flow in my
application:

a.apsx -> b.aspx -> a.aspx

where b.aspx Server.Transfers to a.aspx. Upon return to a.aspx, I want the
form to pick up where it left off, so that the little side trip to b.aspx
doesn't interrupt the user experience.

Thanks,
--kaburke

[kaburke]

The same window.

Thanks,
--kaburke

"Eliyahu Goldin" <re*************@monarchmed.com> wrote in message
news:Ou**************@TK2MSFTNGP12.phx.gbl...

Do you want b.aspx to run in the same browser window or in a different
one?
In the latter case you could start another window on client side without
any
postback in a.aspx.

Eliyahu

"kaburke" <ph**********@hotmail.com> wrote in message
news:YK%Me.202006$tt5.82500@edtnps90...

Is there a way to make a page at the receiving end of a Server.Transfer
think that the request is a Postback? (When I say "think it is a

Postback,"

I mean I want the page to go through the ENTIRE event sequence for a
postback, including LoadViewState, ProcessPostData, etc.) Even when
Sever.Transfer transfers a page to itself (i.e., Page A.aspx contains
Server.Transfer("A.apsx")) the request is seen as a first-time request,

not

a Postback. Is there some way to fool/force the page into thinking the
request is a Postback and run through the entire event gambit, whether it

is

from the same page or not?

To answer the inevitable question, "Why?" I have the following flow in my
application:

a.apsx -> b.aspx -> a.aspx

where b.aspx Server.Transfers to a.aspx. Upon return to a.aspx, I want
the
form to pick up where it left off, so that the little side trip to b.aspx
doesn't interrupt the user experience.

Thanks,
--kaburke

[kaburke]

I found the solution to my problem here:

http://www.codeproject.com/aspnet/Pe...tStatePage.asp

My situation was not identical to the scenario outlined in the article, but
the methods described where easily translated.

Thanks,
--kaburke

"kaburke" <ph**********@hotmail.com> wrote in message
news:YK%Me.202006$tt5.82500@edtnps90...

Is there a way to make a page at the receiving end of a Server.Transfer
think that the request is a Postback? (When I say "think it is a
Postback," I mean I want the page to go through the ENTIRE event sequence
for a postback, including LoadViewState, ProcessPostData, etc.) Even when
Sever.Transfer transfers a page to itself (i.e., Page A.aspx contains
Server.Transfer("A.apsx")) the request is seen as a first-time request,
not a Postback. Is there some way to fool/force the page into thinking the
request is a Postback and run through the entire event gambit, whether it
is from the same page or not?

To answer the inevitable question, "Why?" I have the following flow in my
application:

a.apsx -> b.aspx -> a.aspx

where b.aspx Server.Transfers to a.aspx. Upon return to a.aspx, I want the
form to pick up where it left off, so that the little side trip to b.aspx
doesn't interrupt the user experience.

Thanks,
--kaburke

[Sreejith Ram]

by stating "want the form to pick up where it left off" , i believe you are
looking for the data user entered in the first visit to a.aspx to be
displayed and any changes made to values of controls at server side to be
reflected.

Other than using b.aspx in a popup, do not know of any other default method
supported by asp.net/browser to handle this..

if content of a.aspx and b.aspx is simple, you may try using ASP:PANELs

One way to handle transfering data back and forth between multiple forms is
to use a transaction table in database.
"kaburke" wrote:

a.apsx -> b.aspx -> a.aspx

where b.aspx Server.Transfers to a.aspx. Upon return to a.aspx, I want the
form to pick up where it left off, so that the little side trip to b.aspx
doesn't interrupt the user experience.