S
senfo
I'm in the process of converting an ASP.NET 1.1 application to ASP.NET
2.0 and one of the things I did was to add a MasterPage. The original
1.1 application relies heavily on the Page.Request property to retrieve
values between calls to the Server.Transfer() method. The problem is
that the Page.Request property on the new page does not contain any of
the values from the original page after the transfer.
The original developer used Server.Transfer() rather than
Response.Redirect() for *every* redirect to a new page. This has lead
to a high dependency of the Page.Request property and updating the code
to use, for example, query strings, would be a rather time consuming ordeal.
Does anybody have any suggestions on the easiest approach to get through
this while keeping the code changes to a minimal? I've already started
to save everything to Context and then retrieve it back on the next
page; but, even that has been extremely time consuming and, at times,
difficult because of some irregular implementations.
Thank you in advance,
2.0 and one of the things I did was to add a MasterPage. The original
1.1 application relies heavily on the Page.Request property to retrieve
values between calls to the Server.Transfer() method. The problem is
that the Page.Request property on the new page does not contain any of
the values from the original page after the transfer.
The original developer used Server.Transfer() rather than
Response.Redirect() for *every* redirect to a new page. This has lead
to a high dependency of the Page.Request property and updating the code
to use, for example, query strings, would be a rather time consuming ordeal.
Does anybody have any suggestions on the easiest approach to get through
this while keeping the code changes to a minimal? I've already started
to save everything to Context and then retrieve it back on the next
page; but, even that has been extremely time consuming and, at times,
difficult because of some irregular implementations.
Thank you in advance,