Answer Posted / 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.

Why we are using mvc instead of asp.net? : Asp.Net MVC

1113

---

Explain server control extensibility with reference to asp.net 2.0 ?

1040

---

What is autopostback in dropdownlist in asp net?

1043

---

What is the difference between web config and machine config files?

1065

---

How to comment out asp.net tags?

1105

---

What is css in asp.net?

1125

---

How to implement form based authentication in asp.net application?

1176

---

What does postback mean?

1077

---

What’s the difference between asp.net web forms and asp.net mvc?

1244

---

Is it possible for me to change my aspx file extension to some other name?

1072

---

Explain why datareader is useful?

1046

---

Contrast oop and soa. What are tenets of each16. How does the xmlserializer work? What acl permissions does a process using it require?

1034

---

What is full trust in asp.net?

1174

---

What is the difference between visual basic and asp.net?

1120

---

What is the Intermittent crashing of application in production?

1108

---