I am changing some existing ASP.Net pages. Those pages heavily rely on Response.Redirect. Now I need to carry data between pages, and one obvious option is to change each Response.Redirect to Server.Transfer. This way the modification is very straightforward. However the problem is that Server.Transfer does not change the URL in the address bar, which some see as a problem.

The other option is to rely on PostBackUrl, but the modification seems to be extensive in some cases. For example, say I have two pages P1 and P2, both lead to page P3. P1 has a button B1. In the existing code, when B1 is clicked, it executes a chunk of code (C1) and in the end of C1, it does Response.Redirect. Same with P2, which has a button B2 and only calls Response.Redirect after a major chunk of code (C2) is executed.

Now, if I set PostBackUrl for both B1 and B2 to P3. Where is the best new home for C1 and C2 to reside?

If I follow you, I would say the place to put C1 and C2 is in the code-behind of P3. Them in the OnLoad of P3, you can detect the PreviousPageUrl and run whatever chunk of code you want based on that.

__________________
Visit my blog at http://leedumond.com
Follow me on Twitter: http://twitter.com/LeeDumond

Thanks for your reply!

I thought the same way and that's what I feared - this way, code is a bit messier than what I would like...

Another obvious option is to carry the data as URL parameters. The data I want to carry are of simple scalar types and there are only couple of them, so there is not much trouble to do it this way. The pros are:
1) The code change is very small, and I don't even need to touch those Response.Redirect;
2) Obviously URL's are all correct (since I am not using Server.Transfer)

I initially didn't like this query string solution, since it exposes more information than necessary (and in a obvious way). However that piece of information is not sensitive any way.