Answer Posted / hrdiya

Page processing begins on a thread-pool thread, but that
thread is returned to the thread pool once an asynchronous
I/O operation begins in response to a signal from ASP.NET.
When the operation completes, ASP.NET grabs another thread
from the thread pool and finishes processing the request.
Scalability increases because thread-pool threads are used
more efficiently. Threads that would otherwise be stuck
waiting for I/O to complete can now be used to service
other requests. The direct beneficiaries are requests that
don't perform lengthy I/O operations and can therefore get
in and out of the pipeline quickly. Long waits to get into
the pipeline have a disproportionately negative impact on
the performance of such requests.

What is the difference between adding reference in solution explorer and adding references by using ?

1085

---

In how many ways we can retrieve table records count?

1053

---

Describe briefly what is the role of IIS on an ASP.NET application? What does it for the same application?

1085

---

Define a multilingual website?

975

---

When was asp.net released?

1026

---

which one is more flexibility and reliability and durability asp.net (VS)php which one is best and which one we do nice to create dynamic websites

2163

---

How does windows service lifecycle differ from a .standard. Exe?

1037

---

What are the namespaces used in asp.net mvc? : asp.net mvc

1083

---

What is the exact purpose of http handlers?

1015

---

Will the asp.net validators run in server side or client side? How do you do client-side validation in .net?

966

---

Differentiate between Server.Transfer and Response.Redirect with functionality? Why we can choose one over the other?

1183

---

What is session mode in asp.net?

1055

---

What does asp.net stand for?

1135

---

Can we make activex dll also ti execute in some process as that of client ? How can we do?

4748

---

Which object is used to encapsulate the state of the client and the browser in ASP.NET?

1101

---