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 are the new features implemented in ASP.NET?

1082

---

What is a session in programming?

1074

---

How does asp.net work?

954

---

Where would you use an ihttpmodule, and what are the limitations if any?

1014

---

What are user controls?

1003

---

How to disable validator control by client side JavaScript?

1054

---

What is the use of session state and application state and difference between them?

915

---

Is it possible to apply themes to an asp.net application? If yes, then how?

1011

---

Why is global asax is used for?

1088

---

What kind of programming language is ASP.NET?

1143

---

if i wanna deploy my asp.net project to the production server and situation is that i m still not compiled my project i have as-is on my development side now on production server we dont have a visual studio now what kind of settings i need to be to do in webconfig /machine.config file to deploy my project and in iis too....

2121

---

How can we call webservices in Banking Applications? and where we are using it?

2082

---

What is asp net objects?

1048

---

Distinguish between Server-side and Client-side code?

1085

---

What is scope of an application variable in asp.net?

989

---