Answer / vishal jani

Nitya u r wrong , in server.transfer is reliable then
response.redirect ,server.transfer will not create any
cookie and it will take u on the requested page directly and
taking less time then response.redirect.

Answer / vaibhav nagar

Response.Redirect sends message to the browser saying it to
move to some
different page, while server.transfer does not send any
message to the browser
but rather redirects the user directly from the server
itself. So in server.transfer
there is no round trip while response.redirect has a round
trip and hence puts
a load on server.
Using Server.Transfer you can not redirect to a different
from the server itself.
Example if your server is www.yahoo.com you can not use
server.transfer to move
to www.microsoft.com but yes you can move to
www.yahoo.com/travels, i.e.
within websites. This cross server redirect is possible
only using
Response.redirect.
With server.transfer you can preserve your information. It
has a parameter
called as “preserveForm”. So the existing query string etc.
will be able in the
calling page.

Answer / ramgopal reddy

Server.Transfer is used to post a form to another page.
Response.Redirect is used to redirect the user to another
page or site.

Answer / rohan more

Incase of Server.Transfer ,it doesnot cause rod trip to
client and also it does not store url history and directly
redirect to the requested page without changing URL(Please
note).It transfer from Server itself.

where as in case of Response.redirect it cause round trip
to client browser and then transfer from page which cause
request to redirected page.

Answer / sudhir kunnure

Server.Tranfer direct shows requested page without any
server side roundtrip.
But response.redirect it round trip to server then shows
requested website or page.

Answer / kumar saurabh

In earlier versions of IIS, if we wanted to send a user to a new Web page, the only option we had was Response.Redirect. While this method does accomplish our goal, it has several important drawbacks. The biggest problem is that this method causes each page to be treated as a separate transaction. Besides making it difficult to maintain your transactional integrity, Response.Redirect introduces some additional headaches. First, it prevents good encapsulation of code. Second, you lose access to all of the properties in the Request object. Sure, there are workarounds, but they're difficult. Finally, Response.Redirect necessitates a round trip to the client, which, on high-volume sites, causes scalability problems.
As you might suspect, Server.Transfer fixes all of these problems. It does this by performing the transfer on the server without requiring a roundtrip to the client.

Answer / sulochana singh

Server.Transfer() : client is shown as it is on the requesting page only, but the all the content is of the requested page. Data can be persist accros the pages using Context.Item collection, which is one of the best way to transfer data from one page to another keeping the page state alive.
Response.Dedirect() :client know the physical location (page name and query string as well). Context.Items loses the persisitance when nevigate to destination page. In earlier versions of IIS, if we wanted to send a user to a new Web page, the only option we had was Response.Redirect. While this method does accomplish our goal, it has several important drawbacks. The biggest problem is that this method causes each page to be treated as a separate transaction. Besides making it difficult to maintain your transactional integrity, Response.Redirect introduces some additional headaches. First, it prevents good encapsulation of code. Second, you lose access to all of the properties in the Request object. Sure, there are workarounds, but they're difficult. Finally, Response.Redirect necessitates a round trip to the client, which, on high-volume sites, causes scalability problems. As you might suspect, Server.Transfer fixes all of these problems. It does this by performing the transfer on the server without requiring a roundtrip to the client.

Answer / nitya

Both r used to redirect webform
Server.Transfer fetches page from Server .. while
it will take time..

response.redirect directly open described page..

Where session id is stored?

0 Answers  

what is Satellite Assembly?

2 Answers  

Types of authentications in ASP.NET ?

9 Answers   Accenture, Roland, Shriram,

What is meant by ispostback in asp net?

0 Answers  

You have two buttons in web form and i clicked on one of the button, so how do i find which button i've clicked on the form in my page load?

15 Answers   INDUS,

33) You create English, French, and German versions of your ASP.NET application. You have separate resource files for each language version. You need to deploy the appropriate resource file based on the language settings of the server. What should you do? A . Create an installer and set the Installer.Context property for each version of your application. B . Create an installer that has a launch condition to verify the locale settings. C . Create an installer that has a custom action to install only location-specific files. D . Create an installer that has an MsiConfigureProduct function to install the appropriate version.

2 Answers   Friedkin, ISH, Syntax, Syntax Softtech,

is it possible to persiste customize object in view state? how it is?

2 Answers  

Caching techniques in .NET?

2 Answers   Microsoft,

How cross page posting is done in Asp.net 2.0?

3 Answers  

What is query string? What are its advantages and limitations?

0 Answers  

What is the difference between session object and application object?

0 Answers  

What are various authentication mechanisms in ASP.NET ?

4 Answers   TCS,