Answer / maloy.adhikari

In Both case Same window will open.
I have written the detail diff between two....
.......................................
Server.Transfer vs Response.Redirect:

A common misconception is the difference between
Server.Transfer and Response.Redirect in ASP.NET
applications. Redirect and Transfer both cause a new page to
be processed, but the interaction between the client (web
browser) and server (ASP.NET) is different in each situation.

Redirect: A redirect is just a suggestion – it’s like saying
to the client “Hey, you might want to look at this”. All you
tell the client is the new URL to look at, and if they
comply, they do a second request for the new URL.

If you want to pass state from the source page to the new
page, you have to pass it either on the URL (such as a
database key, or message string), or you can store it in the
Session object (caveat: there may be more than one browser
window, and they’ll all use the same session object).

e.g. Redirect to the page1.aspx page, passing an ID on the
query string. "true" stops processing the current page:

Response.Redirect("page1.aspx?id=100", true);




Transfer: A transfer happens without the client knowing –
it’s the equivalent of a client requesting one page, but
being given another. As far as the client knows, they are
still visiting the original URL.

Sharing state between pages is much easier using
Server.Transfer – you can put values into the Context.Items
dictionary, which is similar to Session and Application,
except that it lasts only for the current request. (search
for HttpContext in MSDN). The page receiving postback can
process data, store values in the Context, and then Transfer
to a page that uses the values.

e.g. Store a message in the context dictionary, and transfer
to the page2.aspx page (which can then display the message):

Context.Items["Message"] = "Your information was changed
successfully";
Server.Transfer("page2.aspx");




Caveats:

* Response.Redirect is more user-friendly, as the site
visitor can bookmark the page that they are redirected to.
* Transferred pages appear to the client as a different
url than they really are. This means that things like
relative links / image paths may not work if you transfer to
a page from a different directory.
* Server.Transfer has an optional parameter to pass the
form data to the new page.
* Since the release version, this no longer works,
because the Viewstate now has more security by default (The
EnableViewStateMac defaults to true), so the new page isn’t
able to access the form data. You can still access the
values of the original page in the new page, by requesting
the original handler:

Diff B/W user control and server control

3 Answers  

---

will this code works fine? or will it gives error? Object obj=5; int i=6; i=i+obj;

1 Answers   Patni,

---

What is is post back property in asp net?

0 Answers  

---

which is faster ArraytList Or Collection ? how? hows the Hashing works internally ?

2 Answers   Emphasis,

---

If there are multiple update panels on the page say upd1 and upd2. There is a button placed in upd1. How can you stop upd2 to update when button placed in upd1 is clicked?

0 Answers  

---

How you can return View from ASP.NET Web API method?

0 Answers  

---

Difference b/w casting and boxing?

5 Answers   IBS,

---

What is a web farm?

0 Answers  

---

Which namespace is used by ado.net?

0 Answers  

---

How to create multi language website in asp.net mvc? : Asp.Net MVC

0 Answers  

---

How does SQL Server session state works

1 Answers   Emphasis,

---

please give a brief knowledge about these events ? page_render() page_prerender() page_unload page_loadcomplete page_preinit

1 Answers   Netsweeper,

---