Answer / justlogin

When a web browser requests a page from a web server, the
web server (IIS) will first check if the request is for an
HTML page. If it is, the request is fulfilled by fetching
the files from the OS and then returning it to the client
(web browser). If the client is requesting an ASP.NET page,
IIS will pass the request to the ASP.NET runtime, which will
then process the application and return the output to the
client.
ASP.NET pages use the .aspx extension. This is to ensure
that ASP.NET is able to run side by side with classic ASP on
the same server, which uses the extension .asp.
One of the inherent problems with the HTTP protocol is its
stateless nature. Put simply, a request made by a user is
loaded into memory, fulfilled, and then unloaded. Subsequent
requests by the same user are treated just like any request;
the server makes no attempt to remember what the user has
previously requested. This stateless nature makes writing
web applications a challenge, because the application
developer must explicitly devise mechanisms to enable the
server to remember the previous state of the application.
Several mechanisms have been devised over the years, such as
cookies and the use of query strings for passing information
to and from the server and the client.
In classic ASP, you typically need to write pages of code in
order to preserve the state of the page after the user has
posted a value back to the server. In ASP.NET, all of these
mundane tasks (collectively known as state management) are
accomplished by the ASP.NET runtime. You will learn more on
this in the following sections.

Answer / zeeshan

when a user places the request on web browser it goes to server thru http request which carries the request towards iis or asp.net web server 2.0 at web server then it calls the processrequest() method to complete the request then finally it produces http-response which sent back to the client which has placed the request this http-response first gets converted into html representation form then can easily be displayed on web browser I think it vl help to the beginners.

Answer / sreyasmn

New in ASP.NET
Better language support
Programmable controls
Event-driven programming
XML-based components
User authentication, with accounts and roles
Higher scalability
Increased performance - Compiled code
Easier configuration and deployment
Not fully ASP compatible

What are the different ways you would consider sending data across pages in ASP (i.e between asp to asp)?

0 Answers  

---

Types of optimization and name a few and how do u do?

1 Answers   Accenture,

---

About Global .asax ?

6 Answers   Satyam,

---

What is difference between web api and web services?

0 Answers  

---

Can we use a static function with a non-static variable?

0 Answers  

---

What is the difference between cache and cookies?

0 Answers  

---

Define viewstate in .net?

0 Answers  

---

What’s the difference between response .redirect and server.transfer?

0 Answers  

---

Explain the difference between codebehind="mycode.aspx.cs" and src="mycode.aspx.cs"?

0 Answers  

---

What are the various types of authentication?

1 Answers  

---

How can we secure the data which is send from client side to server? Like the login id and paasword needs to be authenticated on the server but we cannot send it in plain text into the server.One more thing we are not using the SSL here.

0 Answers   Microsoft,

---

What are the two properties that are common on every validation control?

0 Answers   Siebel,

---