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.

What setting must be added in the configuration file to deny a particular user from accessing the secured resources?

966

---

Which asp.net objects encapsulate the state of the client and the browser?

1022

---

What is asp.net response object?

998

---

To display data in the combo box, prior to setting the Data Source, what kind of property on a Combo Box do you set with a column name?

1002

---

What is a session in asp.net?

986

---

Name the tools or API for developing or testing web api?

905

---

What is the difference between custom controls and user controls?

893

---

Why cyclomatic complexity is important?

971

---

What is advantage of asp.net?

928

---

Define static function?

968

---

What are the Types of authentications in IIS

1001

---

How many types of cache are there?

916

---

Explain the disadvantages of viewstate?

1018

---

What is the difference between Classic ASP and ASP.Net?

1036

---

What is data caching?

920

---